Linux ws-esp16 2.6.27-11-generic #1 SMP Thu Jan 8 08:38:33 UTC 2009 i686 GNU/Linux
$ ./processtest 100 200000
min:0.006ms|avg:0.278-0.520ms|mid:0.475ms|max:141.058ms|duration:107.646s
$ ./threadtest 100 200000
min:0.006ms|avg:0.690-0.768ms|mid:0.715ms|max:235.106ms|duration:159.355s
But if this is a IO problem why monitors does not show a big IO Wait Percentage. It shows a high system usage percentage.
So I suppose that not IO problem seems to be related to process handling inside kernel. May it be related to the preemption model?
I did some additional test:
1.-Change clock timing -> (no improvement)
2.-Change preemption model (tested all of them) -> (no improvement)
3.-Change IO scheduler -> (no improvement)
Is there any way to profile the kernel to see what function gets more attention?
Hi all,
More tests
Linux ws-esp16 2.6.27-11-generic #1 SMP Thu Jan 8 08:38:33 UTC 2009 i686 GNU/Linux 006ms|avg: 0.278-0. 520ms|mid: 0.475ms| max:141. 058ms|duration: 107.646s 006ms|avg: 0.690-0. 768ms|mid: 0.715ms| max:235. 106ms|duration: 159.355s
$ ./processtest 100 200000
min:0.
$ ./threadtest 100 200000
min:0.
But if this is a IO problem why monitors does not show a big IO Wait Percentage. It shows a high system usage percentage.
So I suppose that not IO problem seems to be related to process handling inside kernel. May it be related to the preemption model?
I did some additional test:
1.-Change clock timing -> (no improvement)
2.-Change preemption model (tested all of them) -> (no improvement)
3.-Change IO scheduler -> (no improvement)
Is there any way to profile the kernel to see what function gets more attention?
Hope you find somethig...
I attach a screenshot also...