You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by bryancall <gi...@git.apache.org> on 2017/03/01 18:36:34 UTC
[GitHub] trafficserver issue #1524: Seeing a lot of CPU being used on atomics
GitHub user bryancall opened an issue:
https://github.com/apache/trafficserver/issues/1524
Seeing a lot of CPU being used on atomics
```
- 22.49% 22.20% traffic_server [.] ink_atomic_increment<int, int>
- ink_atomic_increment<int, int>
- 65.31% RefCountObj::refcount_inc
- 88.88% Ptr<ProxyMutex>::Ptr
- MutexTryLock::MutexTryLock
+ 56.95% CacheVC::openReadStartHead
+ 41.89% EThread::process_event
- 11.12% Ptr<ProxyMutex>::operator=
Ptr<ProxyMutex>::operator=
EThread::schedule_local
+ EThread::schedule_in_local
```
----
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] trafficserver issue #1524: Seeing a lot of CPU being used on atomics
Posted by bryancall <gi...@git.apache.org>.
Github user bryancall closed the issue at:
https://github.com/apache/trafficserver/issues/1524
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] trafficserver issue #1524: Seeing a lot of CPU being used on atomics
Posted by bryancall <gi...@git.apache.org>.
Github user bryancall commented on the issue:
https://github.com/apache/trafficserver/issues/1524
I believe this is not really an issue.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---