Linked by Thom Holwerda on Wed 5th Jul 2006 17:09 UTC, submitted by IdaAshley
Linux "The Linux kernel continues to evolve, incorporating new technologies and gaining in reliability, scalability, and performance. One of the most important features of the 2.6 kernel is a scheduler implemented by Ingo Molnar. This scheduler is dynamic, supports load-balancing, and operates in constant time -- O(1). This article explores these attributes of the Linux 2.6 scheduler, and more."
Thread beginning with comment 140620
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[3]: Improving, but still...
by jebb on Thu 6th Jul 2006 07:05 UTC in reply to "RE[2]: Improving, but still..."
jebb
Member since:
2006-07-06

Toolkits can indeed be an issue. Any gtk+ app (the latest Inkscape build comes to mind) feels sluggish on my work XP computer, whereas fluxbox is blazingly fast on my home Arch box. Granted, I should probably check for an update to gtk for windows. But then again, I guess as long as it's not as easy as 'pacman -Syu', I won't bother...

But I believe the parent post also had issues with application start time. I don't think the GHz-count matters much when dealing with multi-MB web browsers, but a faster hard drive (think raptor, or SCSI if you're really serious about that) helps a lot.

Reply Parent Score: 1

GatoLoko Member since:
2005-11-13

Inkscape, as a kde app, uses qt, not gtk.

The use of fluxbox has nothing to do with toolkits, if you use nautilus or konqueror on your fluxbox, you are using gtk or qt.

The apps are using the toolkit nomather what window manager you use.

Reply Parent Score: 1

SEJeff Member since:
2005-11-05

GatoLoko, what are you talking about? Inkscape uses gtkmm. In case you didn't know, gtkmm is c++ bindings to gtk, not qt. Inkscape is a gnome app if you want to go by which toolkit it uses. If you don't believe me, look at the gtkmm code yourself:
http://inkscape.cvs.sourceforge.net/inkscape/inkscape_project/

Reply Parent Score: 1