From: PCMan <pcm...@gm...> - 2014-04-05 11:24:51
|
On Sat, Apr 5, 2014 at 6:09 PM, PCMan <pcm...@gm...> wrote: > On Sat, Apr 5, 2014 at 5:55 PM, PCMan <pcm...@gm...> wrote: >> On Sat, Apr 5, 2014 at 5:53 PM, PCMan <pcm...@gm...> wrote: >>> Hello, >>> here're good news and bad news. >>> The good ones: >>> 1. PCManFM-Qt now fully support Qt 5.1. >>> 2. The X11 related code now uses XCB in Qt5, not Xlib. >> The use of X11 related stuff is minimal. This won't affect our future >> wayland port. >> >>> The bad ones: >>> 1. Qt5 is much heavier than I thought. The memory usage dramatically >>> increased after porting to Qt 5. >>> 2. The Qt5 version of pcmanfm-qt uses about 10-20 MB of resident >>> memory (according to htop). The shared memory increased, too. >> Sorry, I mean the Qt5 build uses "additional" 10-20 MB, which is quite a lot. >> >>> 3. Some weird crashes never happened in Qt 4 were noted. >>> >>> Because of the significant increase of memory usage, I'm not so >>> excited about the port to Qt 5. I'm not sure if there are possible >>> ways to fine tune this part. :-( > > OK, I examined this again with a memeory profiler (massif) and got > some more info. > The most memory hungry part is not in Qt 5. > I ran my desktop inside Virtualbox so the result may be influenced by vbox. > In the report generated by massif, the code used most memory is in > VBoxOGLcrutil.so. > So it's possibly caused by the OpenGL support of virtualbox. > Later I'll try to test it again on my laptop, on which archlinux runs natively. > Cheers! Some more tests are done. I tried to turn off the 3D acceleration support of Virtualbox. Then, I did heap profiling again. This time the memory usage became normal. With process monitor "htop", the resident memory used is still more than that of the Qt 4 version. However, with massif heap profiler, the heap used is decreased. So, overall Qt 5 is not that bad. :-) Cheers! |