Typo 4.0 and memory reduction... 4

Posted by Steve Longdo Fri, 04 Aug 2006 22:56:00 GMT

Have you upgraded to the latest Typo release only to find that it hits the per process memory limit on your host? It happened to me.

Here is how I went about reducing the memory footprint of Typo:
  • Removed sidbars that aren't used from the installation.
    • Amazon through XBox.
  • Removed unused requires from environment.rb
    • In particlular aggregation classes for the Sidebars that were removed.
  • Make sure to not load any unnecessary parts of Rails (i.e. ActiveWebService) That's right I use the admin screen to post!
  • Most importantly deleted the sparklines_textfilter.
That last one makes a huge difference in the memory use of Typo. It removes the need to load RMagick saving around ~8MB from your process size. In fact these changes have brought Typo down to about 33MB in memory. Since the average Rails app uses 30MB this isn't too bad, however memory consumption slowly creeps up over a period of days and hits the limit. Seemingly a memory leak. I will be digging into this issue as time allows, but work is keeping me busy.

I will eventually be using a diferent theme but I switched to this one while checking out memory use and haven't spent enough time on my new one yet.
Comments

Leave a response

  1. Ian Holsman 3 days later:
    How does one stop typo loading activewebservice?
  2. Steve Longdo 3 days later:
    Sorry I should have posted in a bit more detail about that. In environment.rb there is a line that is commented out showing how to ignore ActionWebService and ActionMailer. Just copy the line and uncomment it to get rid of ActionWebService. You could drop ActionMailer as well if you do not want email updates.
    environment.rb
    ...
    Rails::Initializer.run do |config|
    # Skip frameworks you're not going to use
    # config.frameworks -= [ :action_web_service, :action_mailer]
    config.frameworks -= [ :action_web_service]
    ...
    # Also in the config.load.paths remove the line for actionwebservice
    config.load_paths += %W(
    vendor/rubypants
    vendor/redcloth/lib
    vendor/bluecloth/lib
    vendor/flickr
    vendor/syntax/lib
    vendor/sparklines/lib
    vendor/uuidtools/lib
    vendor/jabber4r/lib
    vendor/rails/railties
    vendor/rails/railties/lib
    vendor/rails/actionpack/lib
    vendor/rails/activesupport/lib
    vendor/rails/activerecord/lib
    vendor/rails/actionmailer/lib
    vendor/rails/actionwebservice/lib
    ).map {|dir| "#{RAILS_ROOT}/#{dir}"}.select { |dir| File.directory?(dir) }
    ...
    # This is the other chunk with the aggregation classes
    # Any that you are not using the sidebar for can safely be removed
     $KCODE = 'u'
    require_dependency 'jcode'
    require_dependency 'aggregations/audioscrobbler'
    require_dependency 'aggregations/delicious'
    require_dependency 'aggregations/tada'
    require_dependency 'aggregations/flickr'
    /> require_dependency 'aggregations/fortythree'
    require_dependency 'aggregations/magnolia'
    require_dependency 'aggregations/upcoming'
  3. sterling 20 days later:
    Thanks for the post. I was able to drop my memory usage by over 10 MB on Textdrive so hopefully they won't kill Typo on me any more.
  4. erol 27 days later:
    Thanks for the post! I had a memory leak somewhere in ContentController#preview that knocked down my webserver. After disabling the stuff you recommended I managet to maintain my server up and running for longer than writing one article. ;-) Will look into the preview method, maybe there is a hint why did it happen after all.
Comments