Hi, we've experienced a strange behaviour of the checkpoint procedure. It did occur in 3.466 and occurs in the new 3.5 Version.
Server is debian squeeze running in a xen vm. If you do a import, sometimes sendas checkpoint procedure takes 15-40 minutes. After crashes sometimes it takes so long too, but that might be related to the crash. This is not normal and it occurs only sometimes. Normally a import does take 3-4 minutes. There are some cases where the import is really slow too (not the checkpoint procedure which starts at the end of the import). Because of this we've organized a windows server (32 bit) and this behaviour never occurs there. In our development envorinment (windows 64 bit) this never occured too. But sometimes it just behaves strange and is really slow. Deleting everything and build it from scratch helps. We've tested the prebuild version and build it by ourselves. I've tested a bit on a centos machine which is not running in a vm. I couldn't reproduce the problem until now, but it that might just be luck or coincidence. In general sedna seems to be slower on linux machines, especially when there is large chunk of updates (emails from mutliple users that are linked to several XML elements). Problem is we can't reproduce it (the slow checkpoint procedures issue). Is anybody running sedna in a VM and has experienced anything similar? Perhaps this is related to the VM. On windows it runs fine. Greetings ------------------------------------------------------------------------------ Cloud Services Checklist: Pricing and Packaging Optimization This white paper is intended to serve as a reference, checklist and point of discussion for anyone considering optimizing the pricing and packaging model of a cloud services business. Read Now! http://www.accelacomm.com/jaw/sfnl/114/51491232/ _______________________________________________ Sedna-discussion mailing list Sedna-discussion@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sedna-discussion
