Hi, Can anybody help me to solve this problem? After recataloging the whole web site, I found a very strange problem: it takes about 10 seconds to access a page that may be dynamically generated by DTML methods using catalog. But it is very fast if you just access a static page in the same site by giving url directly. So I guess it is caused by catalog. I search the list for an answer, but I still don't know how to solve it. My zope server is old, it is 2.4. I think upgrading the version is not a choice for me because the server is controled by others, not our group. In addition, some zope concepts confused me. For example, our server actually hosts websites that are developed and maintained by different groups. And each group just manage its own folder. I think zope is better for this model. But when one group uses Zclass, they have to put their own zclass product in the control panel which needs administrative right. Is that weird? If i need to fix the bug in these zclass products, i have to have the right to access the root folder ( the whole zope ) so I can also change the contents belonging to other groups. Why do we put such constraints (zclass in contrl panel)? Why not create control panel for each folder and let each group has it s own private zclass product? Maybe I'm wrong. Thanks. __________________________________ Do you Yahoo!? Yahoo! Finance: Get your refund fast by filing online. http://taxes.yahoo.com/filing.html
From: "Star War" <starwar992001@yahoo.com>
After recataloging the whole web site, I found a very strange problem: it takes about 10 seconds to access a page that may be dynamically generated by DTML methods using catalog. But it is very fast if you just access a static page in the same site by giving url directly. So I guess it is caused by catalog.
Some things that can slow zcatalog down: 1) the first retrieval - indexes are loaded into memory the first time zcatalog is searched. You should see faster retrievals on subsequent searches 2) amount of RAM available vs index size (large index + small RAM = swapping) 3) cache size setting: the default is quite small (Control Panel - Database Management - Cache Parameters, we use a setting of 10000, but it is RAM dependant) 4) number of objects in a single folder. If you have thousands of objects in a single folder the default zope folder can cause you grief (have a look at the BTreeFolder product for a possible replacement) Another option is to install the CallProfiler product and see where the time is being spent. Also, the fast retrieval of static pages could be the result of the page being served from the cache as opposed to being served from zope. A quick & dirty way to test the zope 'serve' of the static page is to manually enter <url>?xxx=abc - this should cause your web server to request the page from zope instead of getting it from the cache (and the page will ignore the parameters), so you can see if there is a difference. HTH Jonathan
Star War wrote at 2004-2-16 11:49 -0800:
After recataloging the whole web site, I found a very strange problem: it takes about 10 seconds to access a page that may be dynamically generated by DTML methods using catalog. But it is very fast if you just access a static page in the same site by giving url directly. So I guess it is caused by catalog.
Install my "ZopeProfiler" product and see what Zope uses it time for: <http://www.dieter.handshake.de/pyprojects/zope> -- Dieter
participants (3)
-
Dieter Maurer -
Small Business Services -
Star War