Re: [SM-USERS] Shared calendar

[Paul L. <pa...@sq...>]

> > > > > > > I'd like to ask you one think about shared Calendar
> > > > > > developed by Paul
> > > > > > > Lesneiwski.
> > > > > > > This plugin is very usefull.
> > > > > > > I have about 5-7 caledars each with 5-8000 users ( email
> > > > > > addresses )
> > > > > > > The problem is that SM got slow when I added those users
> > > > > > into calendars.
> > > > > > > For example main page or calendar list takes about 10
> > > > > > seconds ( before
> > > > > > > it was 1-2 seconds ) I tried to use file backend plugin and
> > > > > > > sql backend plugin but with the same result Is
> > there some tune
> > > > > > options how
> > > > > > > to accelerate the loading of SM more ?
> > > > > >
> > > > > > Can you clarify?  The 5000 to 8000 users are only the
> > > > users who have
> > > > > > shared access to those calendars?  What kinds and how many
> > > > > > events are on the calendars?  I don't currently have
> > development
> > > > time for
> > > > > > this plugin, so I'm not sure I can help you at this
> > time, so you
> > > > > > could dig into it yourself and let us know what you find.
> > > > > > Otherwise, if you can give me more information about the
> > > > issues, I
> > > > > > will look at the issues when this plugin comes to the
> > top of my
> > > > > > list.
> > > > > >
> > > > > > Cheers,
> > > > > >
> > > > > > Paul
> > > > >
> > > > > Thanks for your answer Paul.
> > > > > Yes, 5-8000 users have read access to one calendar. I've
> > > > got about 6
> > > > > calendars (with those thousends users ) and it will
> > grow probably.
> > > > > I would say the problem starts not only with adding of events (
> > > > > the events exists about 20 per month ).
> > > > > First of all it loads very slowly small calendar and it
> > > > means it loads
> > > > > also main page. And when I load the Calendar page and
> > making some
> > > > > actions ( e.g. adding or deleting the events ) it takes
> > about 8-10
> > > > > seconds.
> > > > > I tried to delete all calendars and the pages were loaded
> > > > immediately.
> > > > > I found out when I delete all *.ics form the
> > > > private_calendars folder
> > > > > ( about 1500 ics files ) , the delay was shorter at half.
> > > > > So it means the number of users and private ics files
> > > > somehow affects
> > > > > the pages loading. Events don't affect the delay I really
> > > > appreciate
> > > > > your participation on this and other projects
> > > >
> > > > OK, I understand.  Thank you.  I am very sorry I can't
> > get to this
> > > > right away.  Let me know if you are able to debug it yourself.
> > >
> > >  Hi Paul
> > >
> > > Is there a way how can I debug it myself ? I'd like to do it but I
> > > have no idea how
> >
> > The hard way?  ;-)  I don't have any specific tips, at least
> > not unless I start looking at the code, so all I can say is
> > that I'd put in some echo statements in the plugin code that
> > is being called for the page load, and see which echo
> > statements show before the delay and which ones show after
> > the delay.  Then you can narrow down the offending code.
> > Either that, or start reading and understanding how calendars
> > are loaded into memory; seems like there is a problem in that
> > all users are inspected even when it just needs to look for one user.
>
> I tried to examine shared_clanedar plugin but nothing found. But new
> problem appeared, problem with memory. I tried to load Options-Calendars
> page and I've got error:
>
> Allowed memory size of 33554432 bytes exhausted (tried to allocate 128
> bytes)

Your PHP memory limit could stand to be increased.

> I need to increased in php.ini memory_limit = 64M to work with calendar
> and server.

That's not very unusual for average PHP systems.  I wouldn't consider
that a problem.

> Seems that you were right with loading calendars into memory
> Since the calendars and users are increasing I think in the next weeks I
> will have to disable this plugin cause server will become unavailable
> Don't you know some quick workaround ?

Quick workaround?  You're joking right?

I don't see anything specific yet from you to go on, so I'd just be
guessing even if I had the time to dig into the code, which I do not.
More specific debugging on your end or getting someone (currently not
me, sorry) to help you place debugging output in the plugin would be
my suggested starting points.  I will try to look at the plugin on a
more general level in the future when I have time for it.