Re: [Kolab-devel] event triggered freebusy data generation

Matt Moldvan <[email protected]>
Newsgroups gmane.comp.kde.devel.kolab
Message-ID <CADTR25XNfMoG5TF1+tUjYbDUzOJ4g9=PYLOoqvjtgnEqMnoQ+w@mail.gmail.com>
We've had nothing but trouble with free/busy to the point we had to disable
it (we are still running Kolab 2.3 ish).  65,000+ users now and it kills
the load all of our mailbox servers when it was running through a cron
job...


On Thu, Feb 27, 2014 at 7:29 AM, Thomas Jarosch <
[email protected]> wrote:

> On Tuesday, 25. February 2014 23:06:04 Paul Boddie wrote:
> > > Instead of running kolab-freebusyd every x minutes, for my use-case
> it's
> > > better to start it on demand. So I do so. The freebusy web script
> > > triggers kolab-freebusyd to regenerate and aggregate the data for the
> > > corresponding user, if needed, e.g. if the cached ifb-file is too old.
>
> we sent something similiar upstream back in 2008:
> http://marc.info/?l=kolab-devel&m=120588117817828&w=2
>
> We never had freebusy performance problems ever again.
>
>
> Since the old issue tracker is down, the current
> source code is available here:
> http://www.intra2net.com/en/developer/intranator/download/freebusyd.tar.gz
>
> Cheers,
> Thomas
>
> _______________________________________________
> devel mailing list
> [email protected]
> https://lists.kolab.org/mailman/listinfo/devel
>
>
>

_______________________________________________
devel mailing list
[email protected]
https://lists.kolab.org/mailman/listinfo/devel
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.