SCJP, SCWCD, SCBCD, SCEA 5
SCJP, SCWCD, SCBCD, SCEA 5
Miro Rimo wrote:I see. This is very helpful, many thanks.
For the deployment diagram, how can I assume the average or typical server capability in order to probably size the system?
For instance, if the target availability is 99.99%, this can be achieved in so many ways depending on single server availability, what could the assumption, of each server availability, that can be the starting point of doing the math?
An invisible and ethereal computer will be everwhere and will do evrything
Enzo
...based on this history, determine on runtime which will be the next transaction timeout value needed for the system to address this requirement continuously.
is it really interesting to give up from using CMT in order to garantee your transactions timeout
it would be enough to design a "TransactionProfile" class responsible to log every transaction
SCJP, SCWCD, SCBCD, SCEA 5
Imagine the system is experiencing problems. For example; it may be under extremely heavy load, experiencing networking problems, recovering from a hardware failure, etc. etc. As a result "transactions" are taking around 6 seconds.
No. You can still use CMT and set transaction timeout. You just do it through the app server.
Most app servers already have profiling functionality built in. If your system is experiencing problems it's up to the System Administrator to deal with it - that's their job. Besides, if a system is experiencing extremely heavy load, the app server or infrastructure in general may well implement some kind request throttling. That is, refuse some connections in an attempt to prevent the system from failing completely.
I was told 90% of my transactions should be completed under 5 seconds
SCJP, SCWCD, SCBCD, SCEA 5
Consider Paul's rocket mass heater. |