After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 359703 - Slow speed
Slow speed
Status: RESOLVED DUPLICATE of bug 359197
Product: Pan
Classification: Other
Component: general
pre-1.0 betas
Other Windows
: Normal enhancement
: ---
Assigned To: Charles Kerr
Pan QA Team
Depends on:
Blocks:
 
 
Reported: 2006-10-04 20:21 UTC by Christophe GISQUET
Modified: 2006-10-05 13:10 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Christophe GISQUET 2006-10-04 20:21:48 UTC 
When using a propietary, windows-only, commercial newsreader, I noticed I was pulling much better speed that with pan. The difference is signicative, like 450 versus 650 KB/s. However this unnamed newreader was hogging the CPU, either by agressive scheduling/port monitoring or simply slow algorithm/programming language.

I don't think this can be easily improved, and may be partly due on glib, but I still wanted to mention this fact.
Comment 1 Charles Kerr 2006-10-04 23:16:38 UTC 
Not to ignore the point at hand, but as an aside... what was the CPU usage like on Windows at 450 KB/s?
Comment 2 Christophe GISQUET 2006-10-05 07:34:44 UTC 
The proprietary software: around 30%
Pan: around (less) than 5%
Of course decoding is not considered in that figure.

I think this might be considered a duplicate of bug #359197:
http://bugzilla.gnome.org/show_bug.cgi?id=359197

Contrary to that bug report, I think I have observed the problem for longer, but I don't think it really underlines anything different in the end.
Comment 3 Charles Kerr 2006-10-05 13:10:35 UTC 
Socket polling on Windows and OS X are slower than on Linux,
for different reasons, so g_io_add_watch() is likely to be
the problem in both cases...

*** This bug has been marked as a duplicate of 359197 ***