Legacy Cumulus 1 release 1.9.4 (build 1099) - 28 November 2014
(a patch is available for 1.9.4 build 1099 that extends the date range of drop-down menus to 2030)
Download the Software (Cumulus MX / Cumulus 1 and other related items) from the Wiki
You have probably downloaded an interim zip file, which did not have the complete file set.
Take the zip that is in the first post of this thread, then copy over the new files, or files that you have updated, then put it all onto your web server.
Dont know whether its me or you yet (probably me!), but I downloaded your xml test site and implemented it on my web server (no problems there ). Now I notice that when I have the ajaxindex page open in my browser the CPU on the server goes above 90% and stays there. I get the following (sample) of stuff in my w3 logs.
I opted to include the cumulusdata.xml file in 'realtime' processing so it's being updated every 15 seconds (with my current setup of Cumulus) - this may have some bearing on it!
I'm going in to investigate. I'd appreciate you letting me know if you already know what the problem is, otherwise I'll keep you posted.
Ouch
I suggest you temporarily disable the realtime processing to see what effect that has without changing anything else.
The purpose of the xml was to releive the strain on the systems - a 15 second rewrite on the xml update, and if you left the default, the html page will be placing a refresh call to the server every 3 seconds looking for changing data elements isn't making light of the work, but the server should be able to deal with it.
It will be interesting to see what happens - xmlreturn.php has the cumulusdata.xml file open - Cumulus is trying to re-write it
aadal wrote:3 second to fast for my server so i put it on 15 second and then all fine.
Thanks aadal, that has pointed me in the right direction.
15 second is too fast for my server! I need to use 30!
(The hardware was top of the range in 1999 - not so good now!)
<description>All time low temperature</description>
</item>
- <item name="#TtempH">
<value>at 12:37 on 31 januar 2009</value>
<unit />
<image />
<description>Time of all time high temperature</description>
</item>
- <item name="#TtempL">
<value>at 21:04 on 04 januar 2009</value>
aadal wrote:3 second to fast for my server so i put it on 15 second and then all fine.
Thanks aadal, that has pointed me in the right direction.
15 second is too fast for my server! I need to use 30!
(The hardware was top of the range in 1999 - not so good now!)
Mark
Hi MarkB fine it worked out for you, with 3 second mine go into loop and page takes a long time loading.
My limit was 6 seconds but i set it to 15.
OK I've finished digging. Here's what I uncovered - please shoot me down in flames if I got it wrong!
When ajaxindex.htm loads for the first time it makes 50-odd calls through prototype.js, each of which POSTs xmlreturn.PHP on the server to popoulate each <span> on the page. Each call through xmlreturn.PHP causes it to open the cumulusdata.xml and parse the whole file to extract the one ITEM it was looking for. Every time the Ajax.PeriodicalUpdater is called (at whatever update rate you set it to) it re-parses the xml file another 22 times. (once for each observation value on the page)
This is all too much for my ancient and creaking 10 year old hardware.
The xml concept is great, but I need to find a way of parsing the XML file just once for all of the values (like xmlbanner does). Now you have got me thinking!
MarkB wrote:OK I've finished digging. Here's what I uncovered - please shoot me down in flames if I got it wrong!
When ajaxindex.htm loads for the first time it makes 50-odd calls through prototype.js, each of which POSTs xmlreturn.PHP on the server to popoulate each <span> on the page. Each call through xmlreturn.PHP causes it to open the cumulusdata.xml and parse the whole file to extract the one ITEM it was looking for. Every time the Ajax.PeriodicalUpdater is called (at whatever update rate you set it to) it re-parses the xml file another 22 times. (once for each observation value on the page)
This is all too much for my ancient and creaking 10 year old hardware.
The xml concept is great, but I need to find a way of parsing the XML file just once for all of the values (like xmlbanner does). Now you have got me thinking!
Mark
Hi MarkB
Try thise, and i moved so head load first.
Then it gos days before caling on xml file you need to refresh to update page.