ssossossosso

Forums

Covering OroCRM topics, including community updates and company announcements.  Subscribe

This topic contains 5 replies, has 3 voices, and was last updated by Dima Soroka Dima Soroka 2 years, 9 months ago.

  • Creator
    Topic
  • #4981

    jneto
    Participant

    Hello,

    I’m new to ORO and Symfony, and trying the crm in developer mode, to make some customizations, but i’m worried with the memory usage and the time to process a request.
    Some of the values

    Accounts
    Memory Usage 87.2 MB / 0.0 MB
    Total time 1365 ms

    Dashboard
    Memory usage 136.5 / 0.0 MB
    Total time 1814 ms

    Is this normal ? Can someone give me some feedback about this ?

Viewing 5 replies - 1 through 5 (of 5 total)
  • Author
    Replies
  • #5012

    hemham914
    Participant

    I also experience this problem. I do have a few custom modules but they really don’t do anything too crazy but still the platform seems slow. I thought of trying to install an accelerator for php and seeing if that helps mitigate some of the wait time.

    It could be the caching system inside oro that may or may not be optimized (which is to be expected given the age of the project). All in all it does seem sluggish. Still like it though!


    ~Coding my life away~

    #5021

    jneto
    Participant

    Thanks for the reply.
    My concerns are also the memory usage. I’m evaluating if the platform and the CRM are viable for me, to create some custom applications.

    #5023
    Dima Soroka
    Dima Soroka
    Oro Core

    hi guys

    We are aware of this issue and planning optimization in next few releases.

    #6439

    jneto
    Participant

    Hello, any news about this issue

    #6503
    Dima Soroka
    Dima Soroka
    Oro Core

    We made some improvements but overall picture is around same numbers. Much more work is planned in this direction and results will be available in our end of the year release and earlier next year.

Viewing 5 replies - 1 through 5 (of 5 total)

You must be logged in to reply to this topic.