Mercurial > pidgin
view README.dbus @ 12233:02833a0ae716
[gaim-migrate @ 14535]
SF Patch #1367116 from Michael Carlson
"In profiling gaim, I noticed that on simply starting
CVS gaim, xmlnode_insert_child is using up by far the
most CPU time. After some testing, I realized the
reason why: xmlnode_insert_child is called some 18,000
times on startup, and it is inserting the child at the
end of the list each time, simply by traversing through
the entire linked list. Sometimes this list can have as
many as 800 elements.
This patch adds a variable to the _xmlnode struct,
lastchild, which simply keeps track of the last node in
the list of children. This is then used by
xmlnode_insert_child to insert at the end of the list,
instead of traversing through the whole list each time.
The two relevant functions in xmlnode.c that need to be
updated to keep track of this function appropriately
have been updated.
Running 3 times with and without the change, the
results from oprofile say it all. Here are the measured
number of clock cycles / % of total clock cycles /
function used to simply start and close gaim before the
change:
204 60.7143 xmlnode_insert_child
210 61.4035 xmlnode_insert_child
230 61.8280 xmlnode_insert_child
And after (note that one time no clock cycles were
caught at all)
3 2.5862 xmlnode_insert_child
3 2.5641 xmlnode_insert_child
This affects other areas of the program than just
starting up, but this seems to be the most noticeable
place."
Speed is good. As I was verifying this patch, I added some g_return_val_if_fail() checks.
committer: Tailor Script <tailor@pidgin.im>
author | Richard Laager <rlaager@wiktel.com> |
---|---|
date | Sun, 27 Nov 2005 03:42:39 +0000 |
parents | 2eca9ed49469 |
children |
line wrap: on
line source
This file describes how to compile and run gaim with dbus support. Hopefully, most of the steps from point 3 will soon be automated. 1. Make sure you have the latest version (0.34) of the dbus library installed, including glib bindings. http://www.freedesktop.org/Software/dbus 2. Compile gaim ./configure --enable-dbus make make install 3. Configure your dbus instalation for gaim A. Find your dbus session configuration file, usually /etc/dbus-1/session.conf B. In that file, find the <servicedir> section. This section contains the directory that stores files describing services, usually /usr/share/dbus-1/services C. Copy src/dbus-gaim.service to that directory D. Edit the dbus-gaim.service file you've just copied, and replace the path in the "Exec=" line with the path to your gaim executable. 4. Start Session DBUS if you haven't done it already eval `dbus-launch --session` export DBUS_SESSION_BUS_ADDRESS DBUS_SESSION_BUS_PID These commands will set the two above shell variables. These variables must be set before running any dbus-aware programs. Start gaim as usual. To communicate with it, use "gaim-send". When you execute gaim-send, the dbus system will automatically start a gaim process if one is not running already.