glib vs. no-glib

[new_website85]

An article on QDevBlog can shed a little light on the subject.

Yeah, I read that blog. Unfortunately, it doesn't cover performance. I've googled a bit, and haven't found anything. Since, it hasn't been brought up and people aren't really posting about performance increase/decrease, I'm assuming for now that it is a negligible change in performance. I find this strange, however, because one would think that using a new implementation of something as low level as the eventloop (which accounts for a large percentage of execution time) would definitely change performance one way or another.... The only performance factor I can come up with is the dynamic linker loading the additional libglib.{so,dylib,dll} (if it hasn't been loaded anyways) at program startup - this is of course negligible especially since glib is a relatively small library.

[wysota]

I think the performance change is not significant as both approaches surely try to optimise the thing. Glib is probably a bit slower as it has more features, but has more capabilities and probably proves to be better when multiple apps/libs use it. I don't know how the event loop in Glib works, is it shared between different apps or does every app have a separate instance of the loop?