search

someng / tweetero

Automatically exported from code.google.com/p/tweetero
Other
0 stars 0 forks source link

possible slow connections? #82

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
normal use, connecting from Germany via 3G and/or WiFi, using oAuth.
takes 20-30 seconds for the Home timeline to appear
takes 20-30 seconds for @Mentions to appear
etc.
is anyone else seeing this kind of delay?

Original issue reported on code.google.com by de...@derekunderwood.com on 8 Mar 2010 at 8:25

GoogleCodeExporter commented 9 years ago 
I'm not seeing a delay, but I am getting a lot of 'secure connection failed' 
warnings.

Original comment by npettas@gmail.com on 8 Mar 2010 at 10:42

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
We are investigating what may cause significant delays when handling requests.

Original comment by andriy.v...@gmail.com on 9 Mar 2010 at 5:53

GoogleCodeExporter commented 9 years ago 
We have observed that debug logging was enabled for release configuration. Thus 
from now we disable debug 
logging for the configuration. This may improve performance when parsing a lot 
of xml data received from 
twitter.com.
Please verify this defect and let me know if you still observe significant 
delays.

Original comment by andriy.v...@gmail.com on 10 Mar 2010 at 12:11

GoogleCodeExporter commented 9 years ago 
What is easiest way to disable debug logging?

Original comment by de...@derekunderwood.com on 10 Mar 2010 at 1:21

GoogleCodeExporter commented 9 years ago 
The easiest way is to build "Release" configuration.

Original comment by andriy.v...@gmail.com on 10 Mar 2010 at 3:13

GoogleCodeExporter commented 9 years ago 
Ok, yes, I was building as "release" and I had previously commented out every 
NSLog call, so the debug logging 
was not an issue before, or do I need to make another change in the build 
settings for "release"?

Original comment by de...@derekunderwood.com on 10 Mar 2010 at 4:08

GoogleCodeExporter commented 9 years ago 
No you do not need to make any changes. Just keep your working copy up to date.

Original comment by andriy.v...@gmail.com on 10 Mar 2010 at 4:59

GoogleCodeExporter commented 9 years ago 
I regard the solution of this problem as very risky since we need to change 
application logic.
But at the same time application works as expected.
So I propose to defer this issue to later release cycles.

Original comment by andriy.v...@gmail.com on 10 Mar 2010 at 5:06

GoogleCodeExporter commented 9 years ago

Original comment by andriy.v...@gmail.com on 16 Mar 2010 at 8:35

GoogleCodeExporter commented 9 years ago 
Please see issue 120

Original comment by s.shkrabak@gmail.com on 17 May 2010 at 11:29