On Mon, 2008-11-17 at 14:45 -0500, Steve West wrote:
Steve West wrote:
I am running Fedora 9 x86 64 bit. What is the kernel timetick per
thread? How many threads per second does the kernel run?
Probably not quite what you are asking but here goes:
http://kerneltrap.org/node/464
Steve West wrote:
Steve West wrote:
I am running Fedora 9 x86 64 bit. What is the kernel timetick per
thread? How many threads per second does the kernel run?
Probably not quite what you are asking but here goes:
http://kerneltrap.org/node/464
run for a few seconds:
$ vmstat 1
I am running Fedora 9 x86 64 bit. What is the kernel timetick per thread? How
many threads per second does the kernel run?
Steve--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines:
Steve West wrote:
I am running Fedora 9 x86 64 bit. What is the kernel timetick per
thread? How many threads per second does the kernel run?
Probably not quite what you are asking but here goes:
http://kerneltrap.org/node/464
run for a few seconds:
$ vmstat 1
look at system|in = interrupts
On Mon, 2008-11-17 at 12:49 -0500, Steve West wrote:
Steve West wrote:
I am running Fedora 9 x86 64 bit. What is the kernel timetick per
thread? How many threads per second does the kernel run?
Probably not quite what you are asking but here goes:
http://kerneltrap.org/node/464
run
On Mon, 2008-11-17 at 12:49 -0500, Steve West wrote:
Steve West wrote:
I am running Fedora 9 x86 64 bit. What is the kernel timetick per
thread? How many threads per second does the kernel run?
Probably not quite what you are asking but here goes:
http://kerneltrap.org/node/464
run
Steve West wrote:
I am running Fedora 9 x86 64 bit. What is the kernel timetick per
thread? How many threads per second does the kernel run?
Probably not quite what you are asking but here goes:
http://kerneltrap.org/node/464
run for a few seconds:
$ vmstat 1
look at system|in =
On 17Nov2008 15:19, Steve West [EMAIL PROTECTED] wrote:
The ticks matter when the threads are competing for cpu, but it looks
like in your case they'll mostly be waiting for socket calls (during
which the schedular will hand off to another thread anyway), so
increasing the timeslice frequency
