• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Paul Clapham
  • Ron McLeod
  • Bear Bibeault
  • Liutauras Vilda
Sheriffs:
  • Jeanne Boyarsky
  • Junilu Lacar
  • Henry Wong
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Jj Roberts
  • Tim Holloway
  • Piet Souris
Bartenders:
  • Himai Minh
  • Carey Brown
  • salvin francis

Part 2: Number Concurrent users and performance requirements

 
Greenhorn
Posts: 20
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
How requirements to number of concurrent users affects design? Should we calculate how many server clones to put? Or why do they mention it in the assignment?

Please advise.

Thank you very much.

Vlad
 
Greenhorn
Posts: 5
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Resource contention is your biggest issue. Do you have enough threads/nodes handling concurrent requests? Do you have beefy hardware to support your system? You must look at the whole system from the GUI down to the hardware.
 
Vlad Eroshin
Greenhorn
Posts: 20
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Thank you very much, J!

Does this mean that I should calculate thread and connection pools sizes on the Application server. If that the case where should I put this information in the Assumptions section? Or my deployment diagram must reflect this info?

By the way, what is the good approach to calculate all this? Or just by looking on the specs of the Database and Application Servers.

Please advise,
Vlad
 
Ranch Hand
Posts: 57
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I think the most challenging question is how one can quantify ?

How can one be assured that the system will support so many number of user?

Parag
 
Greenhorn
Posts: 24
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
The answer is hard-work: build prototypes and use simulators and tools like JMeter until defining project architecture.
 
Ranch Hand
Posts: 137
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
As the delivery is just uml and assumptions, isn't the only real option of answering the concurrent user requirement to design it scalable. So that it's easy to add servers as the number of users increase? Prehaps set up a quantity of servers in the deployment diagram?
 
Ranch Hand
Posts: 85
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
i think the big concurrent number means we should design a more flexible framework to meet the non-functional requrments. how to reach such a goal you can describe it in your design.
 
But how did the elephant get like that? What did you do? I think all we can do now is read this tiny ad:
Building a Better World in your Backyard by Paul Wheaton and Shawn Klassen-Koop
https://coderanch.com/wiki/718759/books/Building-World-Backyard-Paul-Wheaton
reply
    Bookmark Topic Watch Topic
  • New Topic