Quote:
Originally Posted by
68topls
Well I would start off by looking at the application and database requirements. IE How big will the database be. Is it read only or read write, How many users, How many simultaneous users, what hardware are they running on ,etc. Probably the easiest way is to look at the development or test environment and take into account the additional resources needed. Things I've learned..... Always predict worse than you actually think (15%) and include a caveat. 8)
This is not "prediction". What you describe is planning.
The original poster asked about predicting system performance (using automated tools).
-----Post Update-----
Quote:
Originally Posted by
System Shock
Maybe I'm reading this wrong, but when you say "Perfom/predict", you are talking about the application named Perform, right? If that is so, Perform can do that for you, or at the very least give you all the data you'd need to make an assessment.
There are hundreds of applications on the Internet named "Perform" ... To discuss a particular application, please post the link.
Thanks.