You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are using J2V8 library in one of our application which is a data hungry application, alot of data flowing in the system. the problem we are facing is because of runtime we are only able to process 20-30 records persecond, where as if I keep one runtime open count reach to the 1000 to 1100 records per second.
Need you suggestion if we can keep one runtime open all the time and what are the pros and cons of it. Along with some steps to manage the running runtime (memory leaks etc).
Thanks
The text was updated successfully, but these errors were encountered:
HI @irbull ,
Hope you are doing well.
We are using J2V8 library in one of our application which is a data hungry application, alot of data flowing in the system. the problem we are facing is because of runtime we are only able to process 20-30 records persecond, where as if I keep one runtime open count reach to the 1000 to 1100 records per second.
Need you suggestion if we can keep one runtime open all the time and what are the pros and cons of it. Along with some steps to manage the running runtime (memory leaks etc).
Thanks
The text was updated successfully, but these errors were encountered: