title: Is g_slice really faster than malloc
body: <p>The GLib docs recommend use of the GLib Slice Allocator over malloc:</p>
  
  <blockquote>
    <p>"For newly written code it is recommended to use the new g_slice API instead of g_malloc() and friends, as long as objects are not resized during their lifetime and the object size used at allocation time is still available when freeing."
    -- <a href="http://developer.gnome.org/glib/unstable/glib-Memory-Slices.html" rel="noreferrer">http://developer.gnome.org/glib/unstable/glib-Memory-Slices.html</a></p>
  </blockquote>
  
  <p>But in practise is g_slice significantly faster than Windows/Linux malloc(faster enough to warrant the extra trouble of handling sizes and GLib's preprocessor hacks like <code>g_slice_new</code>)? I'm planning to use GLib in my C++ program to handle INIish configuration (<code>GKeyFile</code>) and to get access to data structures not available in C++ like <code>GHashTable</code>, so the GLib dependency doesn't matter anyway.</p>