Jump to:

22972 Posts in 11596 Topics by 2824 members

General Questions

SilverStripe Forums » General Questions » SilverStripe performance issues

General questions about getting started with SilverStripe that don't fit in any of the categories above.

Moderators: martimiz, Sean, biapar, Willr, Ingo, swaiba, simon_w

Page: 1 2 3
Go to End
Author Topic: 7382 Views
  • Hamish
    Avatar
    Community Member
    712 Posts

    Re: SilverStripe performance issues Link to this post

    Heh, yeah I went hunting for it and realised that it was handled in Core.php

    Why not bundle it into ManifestBuilder as a static method?

  • DasJacko
    Avatar
    Community Member
    4 Posts

    Re: SilverStripe performance issues Link to this post

    Have you guys thought about building out a memcache-d requirement and using memcache to store that huge manifest of file names/positions and info?

    J.

  • kuba
    Avatar
    Community Member
    5 Posts

    Re: SilverStripe performance issues Link to this post

    > Have you guys thought about building out a memcache-d requirement and using memcache to store that huge manifest of file names/positions and info?

    Don't you think that using memcache is a bit exaggeration for a CMS website?

  • DasJacko
    Avatar
    Community Member
    4 Posts

    Re: SilverStripe performance issues Link to this post

    Sure...exaggeration if we're talking about <1MM pv/month. I'm talking about high-volume, load-balanced use.

  • kuba
    Avatar
    Community Member
    5 Posts

    Re: SilverStripe performance issues Link to this post

    Most CMS websites are not "<1MM pv/month" ones. That's why making memcached obligatory is an exaggeration. Making it optional is something else...

  • DasJacko
    Avatar
    Community Member
    4 Posts

    Re: SilverStripe performance issues Link to this post

    Maybe required was the wrong choice, but if it were an insurmountable performance issue it's not far fetched IMO.

    I think that any implementation worth its salt that uses any 3rd party "requirement" (in this case memcache-d) would be crap unless it had a fall back in case of unavailabilty. Using memcache-d, if you wrap a DB class with the memcache correctly, you code it to default to hitting the DB directly if memcache is not available.

    I'm not sure what you're getting at...was it my semantics? Have I been sufficiently "called out" with "quotations"?

    I was trying to explain that, if memcache were available and you used it on the sections that were causing bottlenecks (provided it's not constantly changing data ala your user profile) it makes a geometric difference in performance.

    FWIW, I've hacked in memcache support for select DB calls (no pun) and have witnessed a 3.5x ability to serve non-static data with a 30 second memcache expiration (or on change expiration rules)...

  • kuba
    Avatar
    Community Member
    5 Posts

    Re: SilverStripe performance issues Link to this post

    Ok, than you didn't want memcached as a requirement but as an option. I agree of course ;)

  • Fuzz10
    Avatar
    Community Member
    786 Posts

    Re: SilverStripe performance issues Link to this post

    >FWIW, I've hacked in memcache support for select DB calls (no pun) and have
    >witnessed a 3.5x ability to serve non-static data with a 30 second memcache
    >expiration (or on change expiration rules)...

    I'm keen on learning what hack you did and how you went about it. ;-)

    Having some issues with a pretty large site a.t.m..... Using APC to store pre-rendered HTML , not the nicest of options... ;-(

    7382 Views
Page: 1 2 3
Go to Top

Want to know more about the company that brought you SilverStripe? Then check out SilverStripe.com

Comments on this website? Please give feedback.