Configured to use Postgres store. Still the same issue. Have you done similar tests? If so, would it be possible for you to share the test scenario? This way, i can see if I have done anything wrong with the tests that i have.
vijay-prismhr
@vijay-prismhr
Posts made by vijay-prismhr
-
RE: Performance degrades as we scale up containers
-
RE: Performance degrades as we scale up containers
Sorry :(. Disabling the studio doesn't make it better. I can see that I can't access the studio anymore. So, the setting is definitely in place. I will try different stores to see if it makes any difference.
-
RE: Performance degrades as we scale up containers
As we are evaluating now, I just have one host (1 VM) now. All the tests with 1,2,5,10 containers were all from the same docker host (Single VM). However, in production, we will either have 4 or 5 hosts. Any reason, why the file needs to be locked for reading? I will definitely try your suggestion about trying a different store.
Thanks for your help. -
RE: Performance degrades as we scale up containers
We have 4 docker hosts. If we can only have 4 js report containers, it defeats the purpose of using Docker. Also, the containers are in its own world. Isolated from one another. Why would a process in one container interfere with another one on the same host?
Note: The hosts are sufficiently provisioned to handle larger loads.
-
Performance degrades as we scale up containers
When we scale docker containers, we are seeing degradation in performance.
Containers avg_response_time error%
1 15 secs 0%
2 25 secs 0%
5 35 secs 10%
10 35 secs 14%I increased the timeouts to 90s for the template engine, script, and chrome. Following is my test scenario.
500 users
120 secs ramp up
1 iteration
Response PDF- 30KBI am using jmeter for running the tests.
Not sure if this is related to the issue I posted earlier
https://forum.jsreport.net/topic/732/error-when-scaling-docker-containers/8 -
RE: Error when scaling docker containers
Thanks for the quick response. I will try building my own image with this change.
-
RE: Error when scaling docker containers
pulled the latest from docker hub yesterday.
Running on centos 7 -
RE: Error when scaling docker containers
That's exactly correct. Whats a proper pattern to deploy when I need to scale?
-
Error when scaling docker containers
When running more than instance of jsreport by scaling up the containers, I get the following error.
2018-09-18T03:21:53.063Z - error: Error when performing remote sync Error: EEXIST: file already exists, open '/app/data/fs.lock'
What am I missing?