Very High memory -IIS Process

5 nop sites on the server two are running 3.5 first one is using 3.5 gigs memory the others are normal 300-450 a normal use site is using same theme and has more traffic..

newer private server 16 gigs mem.

any ideas ..
Thanks

Are they having the same plugins, hosting similar number of products?

I would pull these info and build a stats for comparison. :)

wow you use sql express on a production server, it can only use 1 gb of RAM and would cause more headache when your webs grow up.

Anyway, please input the Nop version, and as Wooncherk said above, you should take a look at on the number of products these sites are using, certainly a small hosting service cannot serve a huge site with millions of products and GBs of traffic.

Also, some of old Nop versions are not memory optimized, so you might want to upgrade to the most recent updates to get the best performance.

At the meantime, you can try to enable 32bit application pool on these sites to lower the RAM usage

1. Right click on the Application Pool and select “Advanced Settings…” or select the same from the Actions pane after selecting the Application pool

2.Change the “Enable 32-bit Applications” to True (if you want the application pool to spawn in a 32-bit mode)

3. Click OK

You can create a dump of memory file and investigate it. It is really possible that a plug in on some circumstances use a lot memory - a stream not closed, stored in memory, some custom draw objects are not disposed,....

Regards,
Boris Todorov

been using Express for many years no issue , dedicated server on a great hosting so not the issue there.

about 1000-1500 products, nop-templetes theme.

if you find solution let me know because we have same issue on dedicated server with 16gb mem, hdd and 8 core xeon. we have also nop-templates theme and 6000 products.

vorodot wrote:

I am downloading the dump file what would I look for its huge...

Thanks

I recall a few times when I was using 3.5 a similar situation happened.  In my case, I had a large number of blog comments that got added by a bot.  Nop was caching thousands and thousands of comments and it inflated my memory everytime the app started.  There are a actually a couple tables that this can happen in 3.5 if you don't use things like captcha, etc.
Do a quick google, search for something like "Sql server show record count in all tables" and run teh query against the nop db that is tied to that worker process from SQL Management studio and then post the results.  This at least will rule out that your memory is not related to normal caching of a table like blogcomments that has been spammed.

Thanks
Chuck

yes, it's true if you open review/comment section without Captcha, it would open to massive spams and wear down the server.

So make sure you setup Recaptcha on all vulnerable points like comments, blog... or simply turn off these features.


Also, on your sql management studio, run this query on every database that is being used by the web to check what table has the biggest size.

SELECT
    t.NAME AS TableName,
    s.Name AS SchemaName,
    p.rows AS RowCounts,
    SUM(a.total_pages) * 8 AS TotalSpaceKB,
    SUM(a.used_pages) * 8 AS UsedSpaceKB,
    (SUM(a.total_pages) - SUM(a.used_pages)) * 8 AS UnusedSpaceKB
FROM
    sys.tables t
INNER JOIN      
    sys.indexes i ON t.OBJECT_ID = i.object_id
INNER JOIN
    sys.partitions p ON i.object_id = p.OBJECT_ID AND i.index_id = p.index_id
INNER JOIN
    sys.allocation_units a ON p.partition_id = a.container_id
LEFT OUTER JOIN
    sys.schemas s ON t.schema_id = s.schema_id
WHERE
    t.NAME NOT LIKE 'dt%'
    AND t.is_ms_shipped = 0
    AND i.OBJECT_ID > 255
GROUP BY
    t.Name, s.Name, p.Rows
ORDER BY
   UsedSpaceKB desc, t.Name

1. Check table size with the above sql query to narrow down what table is causing the problem.


2. Check on log table, maybe Auto Clear Log schedule service is off, it can lead huge table. => Go to admin/system/scheduled tasks => turn on Clear Log

3. repeat step 2 for queuedmail table if it's too big > more than 500 mb.  => delete manually old mail items

4. have recaptcha setup on all weak points like login, registration, blog comment...