Hey there... I'm developing my first major app and I'm running into a frustration here...
I've created a single table database; let's call it "version1". I published it to <webroot>\version1. Performance was pretty quick... no problem here.
My webserver is running on port 81 because we have an antivirus package on the same server that has a web interface. No problem here: I gave access to http://xxx.xxx.xxx.xxx:81/version1 and people have started Data Entry on it.
I then added 3 child tables and created a new gridlinker table/a5w page. I published it at http://xxx.xxx.xxx.xxx:81/version2 so my index.a5w has the parent and 3 children on the page, Lookups and record navigation takes about 5 seconds... again, no problem.
I started working on ../version 3... I made some mods to version 2 and published to ../version3. All I changed was the style and a few formats (display in date, currency, etc.)
Now, when I browse to /version 3, it takes something like SIX MINUTES for the page to generate, and the CPU usage is like at zero... It's not like Alpha5 is busy THINKING or anything... I go back to ../version2 and I get the 5 second response. browse to ../version 3, 5 minutes.
Thinking I'll just try it again, I took version 2 and re-published to version 3. Now version 2 and 3, the SAME database, takes 5 seconds / 5 minutes to load respectively. This got me stumped: Why would the SAME database published in 2 different locations exhibit different behavior? Not to mention a 5-MINUTE response time with no CPU activity.
Any ideas? Thanks!!!!
-Anthony
I've created a single table database; let's call it "version1". I published it to <webroot>\version1. Performance was pretty quick... no problem here.
My webserver is running on port 81 because we have an antivirus package on the same server that has a web interface. No problem here: I gave access to http://xxx.xxx.xxx.xxx:81/version1 and people have started Data Entry on it.
I then added 3 child tables and created a new gridlinker table/a5w page. I published it at http://xxx.xxx.xxx.xxx:81/version2 so my index.a5w has the parent and 3 children on the page, Lookups and record navigation takes about 5 seconds... again, no problem.
I started working on ../version 3... I made some mods to version 2 and published to ../version3. All I changed was the style and a few formats (display in date, currency, etc.)
Now, when I browse to /version 3, it takes something like SIX MINUTES for the page to generate, and the CPU usage is like at zero... It's not like Alpha5 is busy THINKING or anything... I go back to ../version2 and I get the 5 second response. browse to ../version 3, 5 minutes.
Thinking I'll just try it again, I took version 2 and re-published to version 3. Now version 2 and 3, the SAME database, takes 5 seconds / 5 minutes to load respectively. This got me stumped: Why would the SAME database published in 2 different locations exhibit different behavior? Not to mention a 5-MINUTE response time with no CPU activity.
Any ideas? Thanks!!!!
-Anthony
Comment