I have recently moved from Clarity 12.1.1 to 13.3.13 where I am facing issues with Project XOG response times.
In 12.1.1 I was able to extract full project of 3.5 MB in 7 minutes.
In 13.3.13 it's talking 16 minutes for the same project.
JVM Parameter: -Xmx2048m -Xmx4096m -XX:-UseGCOverheadLimit -DforceMemorySettings=false -XX:MaxPermSize=192m -Djava.net.preferIPv4Stack=true
And update "Maximum XML node" settings to 15000000
Did anyone experience such issues?
Do you have any trace enabled on the app server, this might pull down the performance. Also assuming you are using the xog client from 13.3
I am using SOAP client for extract!!!
Also there are no trace enabled.
As I understand you have a big input file, can you please check the count of the tags and if it increases more than 15000000, you may need to increase the Maximum xml node.
Max XML node as something which was introduced in 13.x and we have the performance issues with XOG, performance of XOG is relatively solver than 12.1.3.
Ca recommends to use -1 as max xml node for better performance which helps for better performance of extract(Xog out) but import of big files starts getting fail with " <Description>XOG-9060: The system cannot import this instance with the current configuration. Increase the 'Maximum XML Nodes' value in the CSA and try again.</Description>" error.
If we increase the max xml node to 15000000 or something like that then the import works but export starts talking a lot of time.
The option which I am trying now is to use one server for export with -1 value of max xml node and 15000000 value of max xml node for import.
Please have a look at some of the links
-1 is disabling which is not recommended, what i wanted to know was how many tags you have in your system and what is the memory, incase the file is bigger then the limit specified it will be slow and also with the amount of memory you have allocated.
There is benchmark mentioned on the thread you said so you need to ensure you have adequate amount of memory for the XOG to handle.
The database also comes in picture, if your database is not optimized then also you will face the slowness so you need to check which part it is taking longer by observing the memory utilization on the app server and checking the long running queries at the database levels.
Hope this helps.