Updating recurrence patterns & DB performance.

Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic

   Hi,

I've got my CalendarControl app with custom event handlers (for MySQL)  up-and-running for some time now .

In the beginning (when there was little data to exchange between database and app) performance was smooth.

After a while, CalendarControl.DoReadRPattern event slowed the app down, because of lots of recurrence patterns to retrieve from DB. But problem was resolved implementing caching for the DoReadRPattern event.

But still, when updating a recurrence pattern exception will cause a lot of overhead.

Apparently after the main recurrence pattern gets updated, all of the related events / recurrence exceptions will be forced to be updated (in my case, it will generate about 60 UPDATE queries ).

Is this the normal behaviour? I'm trying to figure out how to update only the event / recurrence exception which got modified instead of all of the related events.

If somebody's got any tips, workarounds, ...

Thanks in advance!

Author	Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic
zotteLORRE Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 31 August 2006 Location: Belgium Status: Offline Points: 5	Post Options Post Reply Quote zotteLORRE Report Post Thanks(0) Quote Reply Topic: Updating recurrence patterns & DB performance. Posted: 29 January 2007 at 5:07am
	Hi, I've got my CalendarControl app with custom event handlers (for MySQL) up-and-running for some time now . In the beginning (when there was little data to exchange between database and app) performance was smooth. After a while, CalendarControl.DoReadRPattern event slowed the app down, because of lots of recurrence patterns to retrieve from DB. But problem was resolved implementing caching for the DoReadRPattern event. But still, when updating a recurrence pattern exception will cause a lot of overhead. Apparently after the main recurrence pattern gets updated, all of the related events / recurrence exceptions will be forced to be updated (in my case, it will generate about 60 UPDATE queries ). Is this the normal behaviour? I'm trying to figure out how to update only the event / recurrence exception which got modified instead of all of the related events. If somebody's got any tips, workarounds, ... Thanks in advance!

sserge Members Profile Send Private Message Find Members Posts Add to Buddy List Moderator Group Joined: 01 December 2004 Status: Offline Points: 1297	Post Options Post Reply Quote sserge Report Post Thanks(0) Quote Reply Posted: 31 January 2007 at 1:15pm
	Regarding your first note about DoReadRPattern... This was fixed in version 10.4. - using Internal cache added. Regarding a second problem about update exceptions... This is an expected behaviour. Recurrence pattern update works as a full update. I think we can optimize simething on this in DataProvider later. As a workaround you can use BeforeEditOperation notification to remember currently editing event. In DoUpdateEvent check whether a currently editing event is a recurrence exception, and skip other exceptions updates. -- WBR, Serge

zotteLORRE Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 31 August 2006 Location: Belgium Status: Offline Points: 5	Post Options Post Reply Quote zotteLORRE Report Post Thanks(0) Quote Reply Posted: 31 January 2007 at 1:33pm
	Thank you very much! With this final, little issue resolved, I've managed to complete my project for 99% now. As a junior developer, I can say that implementing the calendarcontrol was really fun, and that Codejock support is very good. It's a real quality component, and worth the buy! Greets.