[
https://issues.apache.org/jira/browse/TS-1405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13631746#comment-13631746
]
Leif Hedstrom commented on TS-1405:
-----------------------------------
First, I've run the tests at both 1 minute and 5 minute duration, it makes no
difference whatsoever for either patches. How long do I have to run it for?
Your second comment of disabling RAM cache makes no sense. I'm not trying to
test the disk I/O, I'm testing that we don't have regression in processing of
simple requests. Finally, the test you are running it nothing similar to what I
do. You have to change
1) 100 bytes / object (or something smallish, such that each response at least
fits in one TCP segment). I run 100 bytes, because otherwise I become GigE NIC
bound (and that's not what I'm testing).
2) run at least 3x instances of http_load at the same time. That gives a total
of 300 clients. You should run enough clients such that the ATS box gets
bottlnecked on some resource (CPU in my case).
3) Your hardware is probably way, way (I mean, *way*) more powerful than what I
have. I have a quad core i7 with no NUMA (so single socket) and only 1x GigE
network.
I'll run some more tests if you have any ideas of what I should change (other
than turning of RAM cache, that's just not useful). I have one idea of what
could be causing this, so I'll do some more tests today.
> apply time-wheel scheduler about event system
> ----------------------------------------------
>
> Key: TS-1405
> URL: https://issues.apache.org/jira/browse/TS-1405
> Project: Traffic Server
> Issue Type: Improvement
> Components: Core
> Affects Versions: 3.2.0
> Reporter: Bin Chen
> Assignee: Bin Chen
> Fix For: 3.3.2
>
> Attachments: linux_time_wheel.patch, linux_time_wheel_v10jp.patch,
> linux_time_wheel_v11jp.patch, linux_time_wheel_v2.patch,
> linux_time_wheel_v3.patch, linux_time_wheel_v4.patch,
> linux_time_wheel_v5.patch, linux_time_wheel_v6.patch,
> linux_time_wheel_v7.patch, linux_time_wheel_v8.patch,
> linux_time_wheel_v9jp.patch
>
>
> when have more and more event in event system scheduler, it's worse. This is
> the reason why we use inactivecop to handler keepalive. the new scheduler is
> time-wheel. It's have better time complexity(O(1))
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
