That's why I went to this whole serializing system with Storable in the first place- I figured that saving DBI queries would always be a good thing, that is apparently NOT the case when you get large with your structures. I have a database (MySQL) that acts as my data repository- I figured I'd use data structures serialized on-disk to save time, avoiding DBI hits. This is all working, just not at the performance level I expected.
It'd be interesting to find out where the break even point is- How much does serializing performance degrade as your structures get larger and larger? Does it degrade linearally or exponentially?
I'm going to move back to DBI queries, or perhaps to a system that splits up my serialized structures into MUCH smaller chunks.
-Any sufficiently advanced technology is
indistinguishable from doubletalk.
In reply to Re: •Re: Sharing data structures in mod_perl
by Hero Zzyzzx
in thread Sharing data structures in mod_perl
by Hero Zzyzzx
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |