Are you using Postgres ? I suspect the way Sequence Number is implemented doesn't work properly on postgres - so if 2 transactions run at the same time they will receive the same sequence number.
This is not a perfomance issue but a concurrency issue. We'll solve it in one of the next releases.
To use the full functionality of this web site, JavaScript needs to be turned on.
For best results, use the Firefox browser..
Copyright © 2003-2017 - Tersus Software Ltd., All rights reserved. Terms of Use License Graphic design by EmaraDesign
