Hello,
I have a question about memory management. I have performed some space
evaluation when I periodically stored one document into a collection (document
size was approximately 3MB). When I looked at a statistical information about
the document, total size of the document in the database was roughly 1MB, so I
suppose that compression was in ratio 3:1. Weird thing was, that size of a
*.sedata file raised, while the document was periodically stored into the
database, in ratio more than 2:1. When 1000 documents (3GB) were successfully
stored, size of the *.sedata file was approximately 7.5GB.
I want to ask you if this is a normal behaviour or if it is possible that I
have some wrong settings? Or is there a some way how to decrease these space
requirements? I have to admit that this is not so critical issue in these days
but it would be nice to know that it can be decreased somehow.
Thank you for your answer.
Best regards,
Zdenek Sojma
Software Application Engineer I - Test Systems
Engineering Test Services
_______________________Honeywell
Honeywell International s.r.o.
Turanka 100/1387
Brno 627 00, Czech Republic
Phone: +420 532 115 446
Cell Phone: +420 739 626 842
E-mail: zdenek.so...@honeywell.com<mailto:zdenek.so...@honeywell.com>
------------------------------------------------------------------------------
Try New Relic Now & We'll Send You this Cool Shirt
New Relic is the only SaaS-based application performance monitoring service
that delivers powerful full stack analytics. Optimize and monitor your
browser, app, & servers with just a few lines of code. Try New Relic
and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_may
_______________________________________________
Sedna-discussion mailing list
Sedna-discussion@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sedna-discussion
