RE: QoS in Tomcat?

2004-06-01 Thread Shapira, Yoav

Hi,
As an aside, 5.0.26 will have request processor thread priority settable
as an attribute on the connector.

Definitions of QoS are vast and varied.  Asking where to start is kind
of like asking where to start when you write a constitution ;)

Yoav Shapira
Millennium Research Informatics


-Original Message-
From: Rui Zhang [mailto:[EMAIL PROTECTED]
Sent: Friday, May 28, 2004 5:59 PM
To: Tomcat Users List
Subject: Re: QoS in Tomcat?

Good point. I will look into that.

Many thanks.

Rui

On Fri, 28 May 2004, Tim Funk wrote:

 Personally - I would run many instances of tomcat clustered to get
the
 performance you need. It would be much more predictable to maintain.

 -Tim

 Rui Zhang wrote:

  Many thanks, Tim. That at least sounds worth a try... I've got a
valve
  sampling performance data up and running already.
 
  But, Is it sensible we may alter Tomcat to make it QoS-enabled? If
  so, where shall we look at to start?
 
  Best regards,
 
  Rui
 
 
  On Fri, 28 May 2004, Tim Funk wrote:
 
 
 Nope. The spec doesn't spell this out. If your feeling daring, you
could
 write a filter that tries to set and reset the Thread.priorities on
the
fly.
 Then if your JVM pays attention to the thread priorities - you
might
get the
 tweaking you need. (You can also do this in a Valve if you want to
be
lower
 in the stack but I really doubt any of this is useful but its a
great
time
 waster on a cold rainy day)
 
 For example - without all the need try catches ...
 doFilter(...) {
  int newPriority = magicMethodToDeterminePriority(request);
  int oldPriority = currentThread().getPriority();
  currentThread().setPriority(newPriority);
  chain.doFilter();
  currentThread().setPriority(oldPriority );
 }
 
 -Tim
 
 Rui Zhang wrote:
 
 
 Hi all,
 
   Is there any infrastruture availabe (or at least any
possiblities)
in
 Tomcat to tune the QoS requests are receiving?
 
   For instance, is it possible to give differentiated treatments
to
 requests of various importance, by granting them different amount
of
 resources, queueing them differently, etc?
 
   I realise my questions might be a bit vague, as I don't have too
much
 insight about Tomcat. All I'm looking for are some knobs in Tomcat
that we
 can turn to affect its performance, either observed by different
groups of
 requests or by all the requests on a whole. If there are no such
knobs
at
 all, would it be possible to amend the current Tomcat with it?
 
   Any advices (or at least what readings I should do to acquire
that
 knowledge) would be greatly appreciated.


 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




This e-mail, including any attachments, is a confidential business communication, and 
may contain information that is confidential, proprietary and/or privileged.  This 
e-mail is intended only for the individual(s) to whom it is addressed, and may not be 
saved, copied, printed, disclosed or used by anyone else.  If you are not the(an) 
intended recipient, please immediately delete this e-mail from your computer system 
and notify the sender.  Thank you.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: QoS in Tomcat?

2004-05-28 Thread Tim Funk
Nope. The spec doesn't spell this out. If your feeling daring, you could 
write a filter that tries to set and reset the Thread.priorities on the fly. 
Then if your JVM pays attention to the thread priorities - you might get the 
tweaking you need. (You can also do this in a Valve if you want to be lower 
in the stack but I really doubt any of this is useful but its a great time 
waster on a cold rainy day)

For example - without all the need try catches ...
doFilter(...) {
int newPriority = magicMethodToDeterminePriority(request);
int oldPriority = currentThread().getPriority();
currentThread().setPriority(newPriority);
chain.doFilter();
currentThread().setPriority(oldPriority );
}
-Tim
Rui Zhang wrote:
Hi all,
  Is there any infrastruture availabe (or at least any possiblities) in
Tomcat to tune the QoS requests are receiving?
  For instance, is it possible to give differentiated treatments to
requests of various importance, by granting them different amount of
resources, queueing them differently, etc?
  I realise my questions might be a bit vague, as I don't have too much
insight about Tomcat. All I'm looking for are some knobs in Tomcat that we
can turn to affect its performance, either observed by different groups of
requests or by all the requests on a whole. If there are no such knobs at
all, would it be possible to amend the current Tomcat with it?
  Any advices (or at least what readings I should do to acquire that
knowledge) would be greatly appreciated.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


Re: QoS in Tomcat?

2004-05-28 Thread Rui Zhang
Many thanks, Tim. That at least sounds worth a try... I've got a valve
sampling performance data up and running already.

But, Is it sensible we may alter Tomcat to make it QoS-enabled? If
so, where shall we look at to start?

Best regards,

Rui


On Fri, 28 May 2004, Tim Funk wrote:

 Nope. The spec doesn't spell this out. If your feeling daring, you could
 write a filter that tries to set and reset the Thread.priorities on the fly.
 Then if your JVM pays attention to the thread priorities - you might get the
 tweaking you need. (You can also do this in a Valve if you want to be lower
 in the stack but I really doubt any of this is useful but its a great time
 waster on a cold rainy day)

 For example - without all the need try catches ...
 doFilter(...) {
  int newPriority = magicMethodToDeterminePriority(request);
  int oldPriority = currentThread().getPriority();
  currentThread().setPriority(newPriority);
  chain.doFilter();
  currentThread().setPriority(oldPriority );
 }

 -Tim

 Rui Zhang wrote:

  Hi all,
 
Is there any infrastruture availabe (or at least any possiblities) in
  Tomcat to tune the QoS requests are receiving?
 
For instance, is it possible to give differentiated treatments to
  requests of various importance, by granting them different amount of
  resources, queueing them differently, etc?
 
I realise my questions might be a bit vague, as I don't have too much
  insight about Tomcat. All I'm looking for are some knobs in Tomcat that we
  can turn to affect its performance, either observed by different groups of
  requests or by all the requests on a whole. If there are no such knobs at
  all, would it be possible to amend the current Tomcat with it?
 
Any advices (or at least what readings I should do to acquire that
  knowledge) would be greatly appreciated.
 

 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



RE: QoS in Tomcat?

2004-05-28 Thread Ram Mahajan
Can some one tell me how to unsubscribe from this group ?

Thanks
Ram

-Original Message-
From: Rui Zhang [mailto:[EMAIL PROTECTED] 
Sent: Friday, May 28, 2004 3:59 PM
To: Tomcat Users List
Subject: Re: QoS in Tomcat?


Many thanks, Tim. That at least sounds worth a try... I've got a valve
sampling performance data up and running already.

But, Is it sensible we may alter Tomcat to make it QoS-enabled? If so, where
shall we look at to start?

Best regards,

Rui


On Fri, 28 May 2004, Tim Funk wrote:

 Nope. The spec doesn't spell this out. If your feeling daring, you 
 could write a filter that tries to set and reset the Thread.priorities 
 on the fly. Then if your JVM pays attention to the thread priorities - 
 you might get the tweaking you need. (You can also do this in a Valve 
 if you want to be lower in the stack but I really doubt any of this is 
 useful but its a great time waster on a cold rainy day)

 For example - without all the need try catches ...
 doFilter(...) {
  int newPriority = magicMethodToDeterminePriority(request);
  int oldPriority = currentThread().getPriority();
  currentThread().setPriority(newPriority);
  chain.doFilter();
  currentThread().setPriority(oldPriority );
 }

 -Tim

 Rui Zhang wrote:

  Hi all,
 
Is there any infrastruture availabe (or at least any possiblities) 
  in Tomcat to tune the QoS requests are receiving?
 
For instance, is it possible to give differentiated treatments to 
  requests of various importance, by granting them different amount of 
  resources, queueing them differently, etc?
 
I realise my questions might be a bit vague, as I don't have too 
  much insight about Tomcat. All I'm looking for are some knobs in 
  Tomcat that we can turn to affect its performance, either observed 
  by different groups of requests or by all the requests on a whole. 
  If there are no such knobs at all, would it be possible to amend the 
  current Tomcat with it?
 
Any advices (or at least what readings I should do to acquire that
  knowledge) would be greatly appreciated.
 

 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


Re: QoS in Tomcat?

2004-05-28 Thread Tim Funk
Personally - I would run many instances of tomcat clustered to get the 
performance you need. It would be much more predictable to maintain.

-Tim
Rui Zhang wrote:
Many thanks, Tim. That at least sounds worth a try... I've got a valve
sampling performance data up and running already.
But, Is it sensible we may alter Tomcat to make it QoS-enabled? If
so, where shall we look at to start?
Best regards,
Rui
On Fri, 28 May 2004, Tim Funk wrote:

Nope. The spec doesn't spell this out. If your feeling daring, you could
write a filter that tries to set and reset the Thread.priorities on the fly.
Then if your JVM pays attention to the thread priorities - you might get the
tweaking you need. (You can also do this in a Valve if you want to be lower
in the stack but I really doubt any of this is useful but its a great time
waster on a cold rainy day)
For example - without all the need try catches ...
doFilter(...) {
int newPriority = magicMethodToDeterminePriority(request);
int oldPriority = currentThread().getPriority();
currentThread().setPriority(newPriority);
chain.doFilter();
currentThread().setPriority(oldPriority );
}
-Tim
Rui Zhang wrote:

Hi all,
 Is there any infrastruture availabe (or at least any possiblities) in
Tomcat to tune the QoS requests are receiving?
 For instance, is it possible to give differentiated treatments to
requests of various importance, by granting them different amount of
resources, queueing them differently, etc?
 I realise my questions might be a bit vague, as I don't have too much
insight about Tomcat. All I'm looking for are some knobs in Tomcat that we
can turn to affect its performance, either observed by different groups of
requests or by all the requests on a whole. If there are no such knobs at
all, would it be possible to amend the current Tomcat with it?
 Any advices (or at least what readings I should do to acquire that
knowledge) would be greatly appreciated.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


Re: QoS in Tomcat?

2004-05-28 Thread Rui Zhang
Good point. I will look into that.

Many thanks.

Rui

On Fri, 28 May 2004, Tim Funk wrote:

 Personally - I would run many instances of tomcat clustered to get the
 performance you need. It would be much more predictable to maintain.

 -Tim

 Rui Zhang wrote:

  Many thanks, Tim. That at least sounds worth a try... I've got a valve
  sampling performance data up and running already.
 
  But, Is it sensible we may alter Tomcat to make it QoS-enabled? If
  so, where shall we look at to start?
 
  Best regards,
 
  Rui
 
 
  On Fri, 28 May 2004, Tim Funk wrote:
 
 
 Nope. The spec doesn't spell this out. If your feeling daring, you could
 write a filter that tries to set and reset the Thread.priorities on the fly.
 Then if your JVM pays attention to the thread priorities - you might get the
 tweaking you need. (You can also do this in a Valve if you want to be lower
 in the stack but I really doubt any of this is useful but its a great time
 waster on a cold rainy day)
 
 For example - without all the need try catches ...
 doFilter(...) {
  int newPriority = magicMethodToDeterminePriority(request);
  int oldPriority = currentThread().getPriority();
  currentThread().setPriority(newPriority);
  chain.doFilter();
  currentThread().setPriority(oldPriority );
 }
 
 -Tim
 
 Rui Zhang wrote:
 
 
 Hi all,
 
   Is there any infrastruture availabe (or at least any possiblities) in
 Tomcat to tune the QoS requests are receiving?
 
   For instance, is it possible to give differentiated treatments to
 requests of various importance, by granting them different amount of
 resources, queueing them differently, etc?
 
   I realise my questions might be a bit vague, as I don't have too much
 insight about Tomcat. All I'm looking for are some knobs in Tomcat that we
 can turn to affect its performance, either observed by different groups of
 requests or by all the requests on a whole. If there are no such knobs at
 all, would it be possible to amend the current Tomcat with it?
 
   Any advices (or at least what readings I should do to acquire that
 knowledge) would be greatly appreciated.


 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]