Author |
|
PhilC Newbie
Joined: March 18 2004 Location: United Kingdom
Online Status: Offline Posts: 39
|
Posted: February 27 2020 at 19:18 | IP Logged
|
|
|
I am running custom html pages (stored in the PH Web
dir) on a windows tablet and also an android tablet.
The windows tablet performs fine as I can access the
html pages over the local network but the android
tablet has to communicate with PH through HTTP which
is extremely slow. It takes about 15 seconds to load
the page of which 12 of those seconds are waiting for
the server to reply. This is indeed the case using any
machine to talk to the PH server over http. Is there
anything I can do to speed it up?
Thanks,
Phil
|
Back to Top |
|
|
dhoward Admin Group
Joined: June 29 2001 Location: United States
Online Status: Offline Posts: 4447
|
Posted: February 28 2020 at 18:26 | IP Logged
|
|
|
Phil,
Im not sure if I fully understand. If I have this right, a Windows tablet on the same local network as PowerHome has no problem
accessing the webpages (all web pages are accessed as HTTP unless you've actually got a "drive mapping" to the PowerHome web
directory and are accessing the HTML files as a file vs a webpage). An Android tablet however (not sure if it's on the local network
or comes in via the internet or what) is very slow to open the same webpages.
Trying to understand what you're saying, Im assuming that the Windows tablet is indeed mapping the PH directory and directly opening
the HTML files as a file and the Android tablet (probably on the same local network) is accessing the HTML pages as a webpage from
the PH Web server.
If I have that right, Im not quite sure why that would be. Accessing the pages via the webserver will be slower than direct access
as a file as you have more steps involved (PowerHome has to first open the HTML page as a file, read it into memory, and then send it
down a socket using the HTTP protocol) but it shouldnt be that slow. Im not using many custom pages in my own setup but all of pages
render within a second or two whether Im on the local network or internet on both Windows and Android devices.
Do the internal PowerHome pages also take a long time to load or are the reasonably responsive? The custom pages that you're
serving, about how large are they and do they call in alot of different external objects (graphics, javascript libraries, etc)?
I could probably troubleshoot a little better if you could zip up and email me a sample HTML that you're having a problem with along
with any embedded objects. Also, what version of PowerHome are you running?
Thanks,
Dave.
|
Back to Top |
|
|
PhilC Newbie
Joined: March 18 2004 Location: United Kingdom
Online Status: Offline Posts: 39
|
Posted: February 29 2020 at 14:21 | IP Logged
|
|
|
Yes Dave, you have that right. The windows tablet
accesses the html pages over the same network
(file://homeserver/web/music-screen.html) and the
android tablet calls the html like:
http://192.168.1.15:8080/music-screen.html.
Whether it's the android tablet or indeed my laptop the
speed issues are the same. The html files are extremely
small and not graphics heavy.
The issue is how long it is taking the PH server to
respond. For example if I click a link to another page
I will get about 10 seconds of 'waiting for
192.168.1.15' and then when it does respond the page
loads quickly. This behavior is confirmed by looking at
chrome network performance that shows about 10 seconds
of 'waiting time' before anything happens.
Strangely, this issue, however, does not affect any
interaction with PH in terms of clicking buttons to
activate macros etc.
To make matters more confusing, the problem is
intermittent and is sometimes worse than others.
This isn't a massive issue as the functionality is not
affected, it just makes it a pain when I am developing
the html pages as each page refresh is taking so long.
Hope that makes sense!
Thanks,
Phil
|
Back to Top |
|
|
Resolute Newbie
Joined: January 11 2016
Online Status: Offline Posts: 32
|
Posted: March 12 2020 at 20:34 | IP Logged
|
|
|
This has the classic symptoms of DNS resolution issues, not necessarily client to server, but server to resources. Is the webserver using DNS at all in collecting
its resources?
|
Back to Top |
|
|