Pimatic Webinterface needs long time to connect
Wireshark is a tool that records every package that pass your local network interface. It’s very useful to analyse if there are any connection problems.
The hard way could be to start with a config that works and add step by step more options and see which options cause your problem.
Layer 2:
argh…I didn’t scroll down 
Whats about rebuilding your config from scratch? so add your devices to the demo config and keep adding parts of the config until it’s slow again?
ive rebuild my config.
when i add some groups and sort the devices into it, the loading would be slower the more groups i have added and sort devices into it.
when i just add groups the speed is as fast as before. only when i put devices in the group it needs more and more time to load.
same with rulegroups.
can someone please load the web interface with chrome on android and refresh the page. than stop the time from press the refresh button to load the site completely (connecting popup closed).
it needs 7 seconds for me.
thank you guys
@p4co86 said:
when i add some groups and sort the devices into it, the loading would be slower the more groups i have added and sort devices into it.
when i just add groups the speed is as fast as before. only when i put devices in the group it needs more and more time to load.
That’s very interesting. I will look if this can be tweaked.
thx 
But still very strange that you got better performance with the same config and device over WAN.
@sweetpi how are devices loaded? One request per device or all devices with one request?
iam confused, but a have noticed the thing with the groups.
when i add all groups and sort devices into it, it needs 3-4 seconds more to load. the connecting popoup is longer visible.
with sorted devices into the groups
http://fs2.directupload.net/images/150225/b7s8ecan.jpg
without sorted into groups. groups still exist, but devices ar not sorted in.
http://fs2.directupload.net/images/150225/lhid9s85.jpg
@p4co86 I did some optimizations for that in pimatic-mobile-frontend v0.8.47
Could you test if its faster for you?
thanks! Will test it later.
now i have with groups 2 sec. feels a bit better.
but sometimes it feels longer.
maybe there are some other tweaks.
but thanks for that!
@developer since I have installed pimatic v0.9 i have very long socket.io times. Ca. 10 sec.
On rpi via WiFi and on rpi2 with Lan the same long time. I just installed 0.9.
Any ideas what this could be?
Thanks
could no on e help ? herei have attached a screenshot this realy long.
@p4co86 No idea, why socket.io is running wild in your setup. For me as presumably for most users, it works blazingly fast. Socket.io requests are serviced in less than 400ms in my case.
Can you please let me know the file size of your config.json? This is just to get a rough idea of the payload on one of the initial requests which pulls the config. In my case it is 20k and in your does not seem to be much higher. May be it is a load problem with you Raspi. Can you please post some figure, e.g., the summary from “top -n 1”?
https://pimatic.org/shariff-backend/?url=https%3A%2F%2Fpimatic.org%2F
"It always takes longer than you expect, even when you take into account Hofstadter's Law.", Hofstadter's Law
my config file is 76kb.
top -n 1
965 root 20 0 5100 2568 2172 R 19,8 0,5 0:00.09 top
562 root 20 0 13124 10156 3804 S 9,9 2,1 116:08.26 squeezelite-arm
27 root 1 -19 0 0 0 S 4,9 0,0 11:52.22 VCHIQ-0
30592 root 20 0 209128 109164 17864 S 4,9 22,1 12:59.80 node
1 root 20 0 5380 3780 2736 S 0,0 0,8 4:24.86 systemd
2 root 20 0 0 0 0 S 0,0 0,0 0:00.04 kthreadd
3 root 20 0 0 0 0 S 0,0 0,0 2:41.74 ksoftirqd/0
5 root 0 -20 0 0 0 S 0,0 0,0 0:00.00 kworker/0:0H
7 root 0 -20 0 0 0 S 0,0 0,0 0:00.00 khelper
8 root 20 0 0 0 0 S 0,0 0,0 0:00.01 kdevtmpfs
9 root 0 -20 0 0 0 S 0,0 0,0 0:00.00 netns
10 root 0 -20 0 0 0 S 0,0 0,0 0:00.00 perf
11 root 20 0 0 0 0 S 0,0 0,0 0:00.07 khungtaskd
12 root 0 -20 0 0 0 S 0,0 0,0 0:00.00 writeback
13 root 0 -20 0 0 0 S 0,0 0,0 0:00.00 crypto
14 root 0 -20 0 0 0 S 0,0 0,0 0:00.00 bioset
15 root 0 -20 0 0 0 S 0,0 0,0 0:00.00 kblockd
17 root 0 -20 0 0 0 S 0,0 0,0 0:00.00 rpciod
18 root 20 0 0 0 0 S 0,0 0,0 0:00.10 kswapd0
19 root 20 0 0 0 0 S 0,0 0,0 0:00.00 fsnotify_mark
20 root 0 -20 0 0 0 S 0,0 0,0 0:00.00 nfsiod
26 root 0 -20 0 0 0 S 0,0 0,0 0:00.00 kthrotld
28 root 1 -19 0 0 0 S 0,0 0,0 1:59.26 VCHIQr-0
29 root 0 -20 0 0 0 S 0,0 0,0 0:00.00 VCHIQs-0
30 root 0 -20 0 0 0 S 0,0 0,0 0:00.00 iscsi_eh
31 root 0 -20 0 0 0 S 0,0 0,0 0:00.00 dwc_otg
32 root 0 -20 0 0 0 S 0,0 0,0 0:00.00 DWC Notificatio
34 root 20 0 0 0 0 S 0,0 0,0 0:00.00 VCHIQka-0
35 root 0 -20 0 0 0 S 0,0 0,0 0:00.00 deferwq
38 root 20 0 0 0 0 S 0,0 0,0 0:17.44 mmcqd/0
39 root 20 0 0 0 0 S 0,0 0,0 0:04.66 jbd2/mmcblk0p2-
40 root 0 -20 0 0 0 S 0,0 0,0 0:00.00 ext4-rsv-conver
41 root 0 -20 0 0 0 S 0,0 0,0 0:00.00 ipv6_addrconf
56 root 0 -20 0 0 0 S 0,0 0,0 6:43.07 kworker/0:1H
87 root 20 0 8104 3940 3684 S 0,0 0,8 0:45.30 systemd-journal
89 root 20 0 11868 3024 2340 S 0,0 0,6 0:00.62 systemd-udevd
243 root 0 -20 0 0 0 S 0,0 0,0 0:00.00 cfg80211
245 root 20 0 0 0 0 S 0,0 0,0 2:10.68 RTW_CMD_THREAD
294 root 20 0 6680 3572 3204 S 0,0 0,7 0:02.20 wpa_supplicant
358 root 20 0 5060 2384 2188 S 0,0 0,5 0:04.15 cron
361 root 20 0 3844 2432 2176 S 0,0 0,5 0:01.15 systemd-logind
362 avahi 20 0 3864 2644 2372 S 0,0 0,5 0:00.99 avahi-daemon
363 root 20 0 2552 1736 1460 S 0,0 0,4 0:08.74 dhcpcd
365 message+ 20 0 5480 3012 2656 S 0,0 0,6 0:00.90 dbus-daemon
367 root 20 0 9616 5980 4072 S 0,0 1,2 0:22.81 python
369 avahi 20 0 3864 1508 1288 S 0,0 0,3 0:00.00 avahi-daemon
390 root 20 0 31372 3060 2276 S 0,0 0,6 0:07.70 rsyslogd
414 root 20 0 7852 4284 3828 S 0,0 0,9 0:00.14 sshd
448 root 0 -20 0 0 0 S 0,0 0,0 0:00.00 cifsiod
506 nobody 20 0 2280 1456 1336 S 0,0 0,3 0:01.85 thd
528 ntp 20 0 5672 3604 3176 S 0,0 0,7 0:20.46 ntpd
563 root 20 0 4040 1756 1632 S 0,0 0,4 0:00.03 agetty
567 root 20 0 3860 1932 1808 S 0,0 0,4 0:00.03 agetty
1677 root 20 0 0 0 0 S 0,0 0,0 0:02.47 kworker/u2:2
25399 root 20 0 12200 5320 4508 S 0,0 1,1 0:01.55 sshd
25424 root 20 0 4508 3064 2724 S 0,0 0,6 0:00.15 systemd
what is the link you posted for?
@p4co86 said in Pimatic Webinterface needs long time to connect:
Doesn’t look like the system is heavily loaded. Do you have a reverse proxy, e.g. nginx, in the loop?
what is the link you posted for?
Just slipped n by accident. In my setup it is the request with the longest response time. Thus I think the ressource should be possibly shipped with the pimatic frontend.
"It always takes longer than you expect, even when you take into account Hofstadter's Law.", Hofstadter's Law
i try to setup a fresh install and report after that. thanks
i can not remember i have setup a nginx in a loop