With 3.4.66, the core sedata file grows significantly as inserts and updates
are applied.
We have systems with 1 GB of XML data that take up 10 GB of diskspace.
I understand that there are factors beyond raw XML to diskspace size, such
as indexing.
Question
Is file fragmentation still an issue with the latest Sedna RC?
Are there approaches to resolving fragmentation?
Does backup/restore fix the diskspace issue? (Not that I want to implement
backup/restore processes, but just inquiring)
Background
We are utilizing Amazon micro-instances that have a standard 15 GB. We had
planned on worse case scenarios around 6-8 GB per- instance. We are
concerned that sedata diskspace may exceed the 15 GB capabilities.
Thanks,
Malcolm
------------------------------------------------------------------------------
RSA(R) Conference 2012
Save $700 by Nov 18
Register now
http://p.sf.net/sfu/rsa-sfdev2dev1
_______________________________________________
Sedna-discussion mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sedna-discussion
