Editor
Oct 3, 2011 at 3:43 PM
|
Can anyone let me know what is typical for Orchard memory usage? We deployed an Orchard site in a shared environment and are getting warnings that it is using too much memory. At time is is spiking to 230MB. Typically I see it around 180MB on my local
server. Is this normal for the site? It does have a bunch of modules installed and is utilizing the keep alive so it is never getting recycled. Any thoughts on this?
|
|
|
|
Which version of Orchard are u running? It's known that version 1.1 had memory issues.
|
|
Editor
Oct 4, 2011 at 11:57 AM
|
1.2.
On Tue, Oct 4, 2011 at 7:55 AM, rfcdejong <notifications@codeplex.com> wrote:
From: rfcdejong
Which version of Orchard are u running? It's known that version 1.1 had memory issues.
--
Thanks,
Arra
|
|
Coordinator
Oct 4, 2011 at 8:32 PM
|
Around 130MB is typical.
|
|
|
|
rpaquay answered me before, quote:
Currently, if you are looking for the best possible performance, I think (even though I haven't measured) your best bet is to deploy all the module binaires to ASP.NET "~/bin", and remove all source code for modules
and assemblies from "~/Modules/<MyModule>/bin". The second best option would be to remove all source code and leave assemblies in "~/Modules/<MyModule>/bin". This would prevent Orchard from monitoring source code files and also trying
to re-compile modules dynamically.
So if u still have some modules with code in it, place the binary in root bin folder remove them from the Module folder.
|
|