Finally we identified a couple of bottlenecks using MONLBL utility... none of them was the message enqueueing. So, we redid the production and now is feeing more messages to the queue.

Thank you all for your help :-)

I'm using a process that is reading from a global using $order, it's not called by anything external. When removing the call to the BusinessProcess it makes a lot of operations, but when it comes to enqueueing the call it takes several milliseconds. Actually, if I clone the BS and run them at the same time writing to the same queue (even if the queue is Ens.Actor) , I reach the same number of messages than doing it single.

I mean, even working in parallel I cannot increase the number of messages put in the queue. I'm not able to write more than 60-70 per second.

The adapter is Ens.InboundAdapter, but really not using it.

Hi!

Yes, that solution is good. But we need to stop the production to be able to copy the files, and we don't want to to that. We need a way to transfer the data to IRIS without stopping current Ensemble production.

Hi Dmitry,

Thanks for your help, I've been able to compile the class and start the production.

We are using it in a legacy class meant help with the JSON. Anyway, it's working now :-)

Finally I've made some tests. I have duplicated the listglobal changint its values to string, so I can compare two different globals wth the same data but stored differently. Results, show that accessing a list is much slower.

But finally, after reading a bit of doc I found that I could improve the performance by changing the database from 8kb to 64kb. And it really worked:

So

Yes, sorry, my mistake. Actually the line should be:

compared to: 

Thanks to Julius suggestion, I've ran the %SYS.MONLBL analysis tool and clearly something is messing up when trying to get the data from a list:

Thanks David!

But the problem is that that what takes looong time is getting the list values, not throttling over them.

Hi Steve,

Thanks for your help. Finally I got it working and I didn't remember to come here and close the topic. The error was not at Ensemble but at the proxy server.

Thanks anyway.

Hi,

Yes, we have. Actually, that piece of code worked just fine before the authentication was set on place:

#dim callResponse As %Net.HttpResponse = ""
set st = ..Adapter.GetURL(tURL, .callResponse)
If $IsObject(callResponse)
{
}

Now, callResponse is not an object anymore :'(

Yes, I am. This is the class definition:

Class *****.BO.RestOperation Extends EnsLib.REST.Operation {

}