Page History
...
- Certain number of users accessing the server simultaneously (10/20/50/100 users);
- Cache enabled for spell checking purposes;
- Certain hardware and software used (EC2 m5.large instance with 2 CPU and 8 GB RAM);
- Number of words to be checked (1K words or 6K characters);
- Number of spelling and grammar problems in the text (50 grammar problems | 200 misspellings);
- Type of the language used for check (17 default languages).
Testing goal
Our main goal was to observe the response time of text processing and CPU utilization on the server in the case when 10/20/50/100 users send simultaneous requests on various languages to the server with WebSpellChecker v5.5.9.
Environment and testing tool
- We used Apache Jmeter 5.1.1 as a performance measuring tool.
- The machine used was AWS EC2 m5.large instance with 2 CPU and 8 GB RAM.
- The version of the WebSpellChecker Server package is 5.5.9 (released on April 21, 2020).
Testing process
We have run our tests continuously increasing the number of users accessing it for each of the languages in the default language group (17 languages). The cache setting was enabled for all set sets of tests. The following combinations of text to be checked are used for each language and for each user tier:
- 1K words (6K characters) with 50 grammar problems, 200 misspellings;
- 1K words with 50 grammar problems only;
- 1K words with 200 misspellings only.
The measured was were the response time and CPU utilization.
Observations
Our observations are presented in the charts below.
Response time and CPU utilization (only 200 misspellings)
Chart below represents response time results aggregated by language and user tiers when there are only 200 misspellings in text of 1K words size.
...
Chart below represents CPU utilization results aggregated by language and user tiers when there are only 200 misspellings in text of 1K words size.
Response time and CPU utilization (only 50 grammar problems)
Chart below represents response time results aggregated by language and user tiers when there are only 50 grammar problems in text of 1K words size.
...
Chart below represents CPU utilization results aggregated by language and user tiers when there are only 50 grammar problems in text of 1K words size.
Response time and CPU utilization (200 misspellings and 50 grammar problems)
Chart below represents response time results aggregated by language and user tiers when there are200 misspellings and 50 grammar problems in text of 1K words size.
...
Chart below represents CPU utilization results aggregated by language and user tiers when there are 200 misspellings and 50 grammar problems in text of 1K words size.
Findings and recommendations
Here are the outcomes and aftermath as well as our advice on hardware and software requirements and notes on performance issues which users may encounter:
...
