Alkacon newsletter admin performance

View: New views
3 Messages — Rating Filter:   Alert me  

Alkacon newsletter admin performance

by mikedikan :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Hello,

I am using opencms 7.0.5 and the oamp newsletter module 1.0.1, and  
have migrated into opencms a newsletter user base of roughly 100,000  
users.  I am running into some serious performance issues in the  
newsletter admin page for 'subscriber management' and find that it  
takes in the 10's of minutes for these pages to load.  At first I  
thought that I might be able to speed things up on the DB side by  
adding some indices, but that turned out to be a dead end, as  
everything that should be indexed already is. Watching the database  
logs, it looks like the subscriber page is loading all of the data in  
the 'CMS_USERDATA' table for all of the users, not just the current  
result-set.  Has anyone else run into this problem and found a good  
way to speed things up?

Thanks,
Mike

_______________________________________________
This mail is sent to you from the opencms-dev mailing list
To change your list options, or to unsubscribe from the list, please visit
http://lists.opencms.org/mailman/listinfo/opencms-dev

Re: Alkacon newsletter admin performance

by mikedikan :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

No one has any tips?  I'd be happy to provide more details if necessary.

On Oct 1, 2009, at 9:47 PM, Mike Dikan wrote:

> Hello,
>
> I am using opencms 7.0.5 and the oamp newsletter module 1.0.1, and  
> have migrated into opencms a newsletter user base of roughly 100,000  
> users.  I am running into some serious performance issues in the  
> newsletter admin page for 'subscriber management' and find that it  
> takes in the 10's of minutes for these pages to load.  At first I  
> thought that I might be able to speed things up on the DB side by  
> adding some indices, but that turned out to be a dead end, as  
> everything that should be indexed already is. Watching the database  
> logs, it looks like the subscriber page is loading all of the data  
> in the 'CMS_USERDATA' table for all of the users, not just the  
> current result-set.  Has anyone else run into this problem and found  
> a good way to speed things up?
>
> Thanks,
> Mike


_______________________________________________
This mail is sent to you from the opencms-dev mailing list
To change your list options, or to unsubscribe from the list, please visit
http://lists.opencms.org/mailman/listinfo/opencms-dev

Re: Alkacon newsletter admin performance

by Florian Heinisch :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Hi Mike,

sorry, I over read your first email concerning this issue.
I only can confirm that browsing through the subscriber list in the  
newsletter admin page was already slow with 8.000 users. I did not get  
into details to find the reason for that. You'd probably have to take  
a look at the source code to find out. If it turns out that the whole  
user table gets loaded for every page the SQL queries have to be  
modified to return paginated lists.

Kind regards,

Florian

On Oct 13, 2009, at 2:36 AM, Mike Dikan wrote:

> No one has any tips?  I'd be happy to provide more details if  
> necessary.
>
> On Oct 1, 2009, at 9:47 PM, Mike Dikan wrote:
>
>> Hello,
>>
>> I am using opencms 7.0.5 and the oamp newsletter module 1.0.1, and
>> have migrated into opencms a newsletter user base of roughly 100,000
>> users.  I am running into some serious performance issues in the
>> newsletter admin page for 'subscriber management' and find that it
>> takes in the 10's of minutes for these pages to load.  At first I
>> thought that I might be able to speed things up on the DB side by
>> adding some indices, but that turned out to be a dead end, as
>> everything that should be indexed already is. Watching the database
>> logs, it looks like the subscriber page is loading all of the data
>> in the 'CMS_USERDATA' table for all of the users, not just the
>> current result-set.  Has anyone else run into this problem and found
>> a good way to speed things up?
>>
>> Thanks,
>> Mike
>
>
> _______________________________________________
> This mail is sent to you from the opencms-dev mailing list
> To change your list options, or to unsubscribe from the list, please  
> visit
> http://lists.opencms.org/mailman/listinfo/opencms-dev


_______________________________________________
This mail is sent to you from the opencms-dev mailing list
To change your list options, or to unsubscribe from the list, please visit
http://lists.opencms.org/mailman/listinfo/opencms-dev