Re: [ZODB-Dev] Sharing (persisted) strings between threads
That is already possible: just use RelStorage with memcached and set your ZODB cache size to zero or something small. Â However, large ZODB applications typically depend on a large number of persistent objects to respond to even the simplest requests, so you would have to optimize the application to load as few objects as possible. Related: http://plone.293351.n2.nabble.com/Prevent-simultaneous-logins-in-Plone-tp5724869p5729428.html -- Mikko Ohtamaa mFabrik - Freedom Delivered. Web site - http://mfabrik.com Mobile site - http://mfabrik.mobi Blog - http://blog.mfabrik.com ___ For more information about ZODB, see the ZODB Wiki: http://www.zope.org/Wikis/ZODB/ ZODB-Dev mailing list - ZODB-Dev@zope.org https://mail.zope.org/mailman/listinfo/zodb-dev
[ZODB-Dev] When will the Data.fs.index will be touched
Hi, I'm Axel Gerke, yet another zope developer. My question is: Under what circumstances will the Data.fs.index be touched (i.e. its timestamp changes)? After consulting Andreas Jung, he can only remember, the file will be only touched @ startup or shutdown. But we see that the file's timestamp changed at runtime. Can someone tell me at which operations the Data.fs.index will be touched? thx and cheers, Axel ___ Neu: WEB.DE De-Mail - Einfach wie E-Mail, sicher wie ein Brief! Jetzt De-Mail-Adresse reservieren: https://produkte.web.de/go/demail02 ___ For more information about ZODB, see the ZODB Wiki: http://www.zope.org/Wikis/ZODB/ ZODB-Dev mailing list - ZODB-Dev@zope.org https://mail.zope.org/mailman/listinfo/zodb-dev
[ZODB-Dev] ZODB packing and possible side effects?
Hi all, I'm trying to read up on ZODB packing and possible side effects. Does anyone know about comprehensive docs on this? Think interaction with repozo backup processes, a pack removing weakly referenced objects, impact on the Data.fs index, ... Thanks for any hints! Sincerely, Mark -- Mark Van den Borre Noormannenstraat 113 3000 Leuven, België +32 486 961726 ___ For more information about ZODB, see the ZODB Wiki: http://www.zope.org/Wikis/ZODB/ ZODB-Dev mailing list - ZODB-Dev@zope.org https://mail.zope.org/mailman/listinfo/zodb-dev
Re: [ZODB-Dev] When will the Data.fs.index will be touched
On 09/12/2010 12:25, Axel Gerke wrote: I'm Axel Gerke, yet another zope developer. My question is: Under what circumstances will the Data.fs.index be touched (i.e. its timestamp changes)? After consulting Andreas Jung, he can only remember, the file will be only touched @ startup or shutdown. But we see that the file's timestamp changed at runtime. Can someone tell me at which operations the Data.fs.index will be touched? I would also like to know. I've had cases where Data.fs.index hasn't been touched in several days (the modified time stamp shows a date several days ago), on sites that are very active (in other words, its unlikely that nothing changed). If I then restart the zeo, I find that it takes a very long time, perhaps because it needs to reindex. I usually delete the old .index file (which appears to be stale) so that it can create a new one. Something happens and the zeo server stops writing to Data.fs.index. Unfortunately this very vague description is all I have right now, I've done no deeper investigation yet. regards, Izak ___ For more information about ZODB, see the ZODB Wiki: http://www.zope.org/Wikis/ZODB/ ZODB-Dev mailing list - ZODB-Dev@zope.org https://mail.zope.org/mailman/listinfo/zodb-dev
Re: [ZODB-Dev] When will the Data.fs.index will be touched
On Thu, Dec 9, 2010 at 5:25 AM, Axel Gerke axel.ge...@web.de wrote: Hi, I'm Axel Gerke, yet another zope developer. My question is: Under what circumstances will the Data.fs.index be touched (i.e. its timestamp changes)? After consulting Andreas Jung, he can only remember, the file will be only touched @ startup or shutdown. But we see that the file's timestamp changed at runtime. Can someone tell me at which operations the Data.fs.index will be touched? It's written on shutdown, pack and on startup if there was no index or if the index was out of date. In some versions of ZODB, the index was periodically written after a certain amount of growth although the algorithm was flawed in such a way that when the database grew large, the index was almost never written due to growth. Note before ZODB 3.10, it could take a long time to write an index for a large database. It could take so long that zdaemon, with it's default timeout setting would do a hard kill of the process before it had a chance to finish writing an index. In ZODB 3.10, index writing now only takes a few seconds. If you're using ZODB 3.9 or earlier, you should use the zdaemon backoff-limit option to configure zdaemon to wait much longer before doing a hard kill. Jim -- Jim Fulton ___ For more information about ZODB, see the ZODB Wiki: http://www.zope.org/Wikis/ZODB/ ZODB-Dev mailing list - ZODB-Dev@zope.org https://mail.zope.org/mailman/listinfo/zodb-dev
Re: [ZODB-Dev] ZODB packing and possible side effects?
On Thu, Dec 9, 2010 at 5:32 AM, Mark Van den Borre m...@markvdb.be wrote: Hi all, I'm trying to read up on ZODB packing and possible side effects. Does anyone know about comprehensive docs on this? Documentation is a major weakness of ZODB. Think interaction with repozo backup processes, I don't use repozo myself, but I believe it detects packs and makes a full backup after a pack. a pack removing weakly referenced objects, I'm not sure what you're referring to or if you have a question. impact on the Data.fs index, ... A new index file is created after a pack. Jim -- Jim Fulton ___ For more information about ZODB, see the ZODB Wiki: http://www.zope.org/Wikis/ZODB/ ZODB-Dev mailing list - ZODB-Dev@zope.org https://mail.zope.org/mailman/listinfo/zodb-dev
Re: [ZODB-Dev] ZODB packing and possible side effects?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 12/09/2010 05:32 AM, Mark Van den Borre wrote: I'm trying to read up on ZODB packing and possible side effects. Does anyone know about comprehensive docs on this? Think interaction with repozo backup processes, a pack removing weakly referenced objects, impact on the Data.fs index, ... - - Repozo detects packs, and forces a full backup after one, even if you request an incremental. - - You need to explain what you mean by weakly referenced. - - Pack causes the index to be written. Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk0A90oACgkQ+gerLs4ltQ6tKwCfdd/XWm5zsYhuEUid7NxCmS1W sLEAoNI6YRioiukHoV7kEtDSGM+ifxsS =u09G -END PGP SIGNATURE- ___ For more information about ZODB, see the ZODB Wiki: http://www.zope.org/Wikis/ZODB/ ZODB-Dev mailing list - ZODB-Dev@zope.org https://mail.zope.org/mailman/listinfo/zodb-dev
