Forum Discussion
I have read the page you recommend, but it did not solve my problems with web testing. That page is about general ideas, nothing spesific.
I have read that page before, and re-read after your post, I also read some other pages linked from there.
Yeah , there is some description of each results in the log pages and in the analysis page, but that is not enough..
In the page you wrote me says that,
"Performance testing helps you understand how your application will behave as more users visit your web site. "
it says, it helps me understand how my application will behave, yeah but how exactly ?
In the given points below from that help page, I want to ask questions for every point there;
- How does the server’s response time change if you increase or decrease the number of users?
What you mean by server's response time change ? Even if there is 5 or 10 users, response time changes.
How big a change I have to wait to say there is a problem ? How to measure this response time ? for spesific requests ?
For each requests ? For each connection ? Or for total request time ? Request execiton number ?
Why there is no example calculations in the help ? Is this so hard to explain ?
- How many users can simultaneously work with a web server without a perceptible slowdown?
What you mean by perceptible sllowdown ? with much vuser, the test slow down.
- What load can crash the server application?
what you mean by crash ? Sometimes a test crushes even with small numbers of vuser due to some uncommon errors..
So whenever there is an error, that means server crash ? With which errors Exatcly? (I do not count warnings here.. which is another issue)
- How do hardware and software changes affect the server performance?
What to do in order to measure server response time due to our test results ?
Server performance, yes but how will I check this performance ?
Can you explain this step by step ?
Can you suggest some ways to read anaylsis resutls ?
Can you give some real life examples ?