Skip to content
This repository has been archived by the owner on Dec 4, 2018. It is now read-only.

EpiCurl causes CPU spike under heavy usage (reported by @alombarte #1

Closed
jmathai opened this issue May 9, 2009 · 1 comment
Closed

Comments

@jmathai
Copy link
Owner

jmathai commented May 9, 2009

Debugging information from the server the problem was seen on:

PING twitter.com (128.121.146.228) 56(84) bytes of data.
64 bytes from 128.121.146.228: icmp_seq=1 ttl=240 time=160 ms
64 bytes from 128.121.146.228: icmp_seq=2 ttl=240 time=158 ms 64 bytes from 128.121.146.228: icmp_seq=3 ttl=240 time=162 ms 64 bytes from 128.121.146.228: icmp_seq=4 ttl=240 time=165 ms 64 bytes from 128.121.146.228: icmp_seq=5 ttl=240 time=165 ms

PING search.twitter.com (128.121.146.107) 56(84) bytes of data.
64 bytes from 128.121.146.107: icmp_seq=1 ttl=240 time=171 ms
64 bytes from 128.121.146.107: icmp_seq=2 ttl=240 time=175 ms 64 bytes from 128.121.146.107: icmp_seq=3 ttl=240 time=170 ms 64 bytes from 128.121.146.107: icmp_seq=4 ttl=240 time=175 ms

$ time curl http://twitter.com/statuses/public_timeline.xml real 0m0.888s user 0m0.004s sys 0m0.000s

curl --trace-time http://twitter.com/statuses/public_timeline.xml > test.test % Total % Received % Xferd Average Speed Time Time Time Current

                         Dload  Upload   Total   Spent    Left  Speed

100 18535 100 18535 0 0 8513 0 0:00:02 0:00:02 --:--:-- 9593

@jmathai
Copy link
Owner Author

jmathai commented May 11, 2009

Fixed cpu usage in EpiCurl. Problem reported by splitweet devs.
Closed by 68d03f6

This issue was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant