Database overhead on profiles with presence can get high. Putting phones that don't need presence (either on the phone or that phone being watched) on profiles without presence enabled will make a big difference. Keeping your register and subscription times very high (8 hrs maybe?), and spread out (not happening all at the same time, there are some settings to randomize this) will also make a big difference. Disk io on the db becomes an issue as you push this too far. In the end, testing is the best way too know when you are pushing it too far. On Thursday, September 17, 2015, Yehavi Bourvine <yehavi.bourvine@gmail.com> wrote:
Hello,
We currently have over 500 extensions, most of them sharing the same profile which has presence enabled (since some of them need shared lines and BLFs). I am now watching the future of having over 6,000 extensions on that PBX. So' I have a few questions:
- Does having all the phones on the same profile can induce performance problems which we won't face if we split them among a few profiles? - Is there a difrerence (mainly database access) between placing all phones that need presence on the same profile vs. splitting them to 3-4 profiles? - About 2/3 of the phones do not really need presence; however, it is more comfortable for me to put them on the same profile. Will the databases access due to presence events might be so high that I should invest the effort to put the single line phones on a different profile without presence?
Thanks, __Yehavi: