ConferenceRoom 3.5

Platform Notes



Last Updated: July 11, 2007

Latest Release:3.5.0.2

Jump to:
[Windows 95/98/Me] | [Windows NT] | [Windows 2000] | [Windows XP/2003/Vista] | [Linux]
[FreeBSD] | [Solaris 10 Sparc 7] | [Darwin OSX10]


Windows 95/98/Me

ConferenceRoom is not supported on Windows 95, 98, and ME. The builds may work, but at a minimum you will encounter performance problems. These are just not server operating systems.


Windows NT 4.0 Workstation and Server with Service Pack 5, 6, or 6a

These platforms run ConferenceRoom excellently. 6,000 concurrent connections can be sustained without difficulty. 10,000 connections can be achieved with proper tuning and adequate RAM. Performance is exceptional.

NT Workstation does not have NT Server's resistance to certain TCP denial of service attacks. We recommend that any critical servers be run on the Server version of NT. However, so long as the machine isn't attacked, ConferenceRoom will run excellently on NT Workstation.

Note that prior versions of Windows NT are not supported. NT4.0 is not officially supported without at least Service Pack 5.


Windows 2000

Windows 2000 runs ConferenceRoom excellently. 6,000 concurrent connections can be sustained without difficulty. 10,000 connections can be achieved with proper tuning and adequate RAM. Performance is exceptional.

We recommend installing Service Pack 2 as it resolves several networking problems that can affect ConferenceRoom. The most serious of these problems can cause the server to crash under heavy load.

Some users have reported encountering problems installing ConferenceRoom with Windows 2000's Terminal Server features enabled. A workaround is to disable Terminal Server, install ConferenceRoom, and then enable Terminal Server. We suggest you try the installer before using the workaround, in most cases it will work without a problem.


Windows 2003/XP/Vista

These versions of Windows run ConferenceRoom excellently. 6,000 concurrent connections can be sustained without difficulty. 10,000 connections can be achieved with adequate RAM. Performance is exceptional.

Note that non-server Windows operating systems cannot resist certain types of denial-of-service attacks as well as server-class operating systems can.


Solaris 10 (Sparc v7+)

Solaris runs ConferenceRoom excellently. No problems have been reported with this build.

Make sure you correctly set your per-process resource limits and kernel limit on the maximum number of files a single process can have open. Network connections count as files.

ConferenceRoom will use the /dev/poll interface where it is available. This results in even higher performance. See the PLATFORM file if you need to disable this for some reason.


Linux 2.5 and 2.6 (x86)

Linux runs ConferenceRoom well. 1,000 concurrent connections can be supported easily. 10,000 can be achieved with the right kernel version and proper tuning. Kernel versions that do not support NPTL and futexes are not supported. Kernel releases of 2.5 from 2004 and later should work fine.

A common problem on Linux machines is restrictive ulimit settings. You can see your ulimit settings by typing ulimit -a (assuming you are using the bash shell). Look closely at the number of open files, cpu time, max user processes, and virtual memory limits. Note that the limit on the number of process must be high because Linux counts each thread of each server as a process. If necessary, add commands to change the limits to your startcr script or talk to your system administrator.

You can also use the tuning options documented in the PLATFORM file.

This build also works on 64-bit versions of Linux.


FreeBSD

ConferenceRoom 3.5 supports FreeBSD 4.1 and later builds, RELEASE or STABLE. Releases of FreeBSD 4.0 from the STABLE stream dated 2001 or later should also work.


Darwin (OS-X for x86 and PPC)

This platform is still experimental. No problems are known.

You may need to adjust your resource limit on the number of file descriptors. We recommend installing GNU bash and changing the startcr script to use bash. This will allow you to add a line like ulimit -n 16384 to your startcr script to ensure ConferenceRoom does not run out of file descriptors.

You can also use the platform tuning options documented in the 'PLATFORM' file. KQUEUE support is experimental and disabled by default. The 'PLATFORM' file explains how to enable this if you wish to.


Maintained by David Schwartz, questions may be sent to WebMaster Support

All Trademarks are property of their respective owners

Contents Copyright (C) 1999-2007, WebMaster


New platforms can be added on customer request. Let us know if we do not support your preferred platform.