Page 1 of 1

Thin@ Application Server Hardware Requirements

Posted: Fri Nov 12, 2010 7:40 pm
by dpavlic
Quick recommended configurations for a Thin@ Server
These are the most common hardware configurations used for a Thin@ Server:

1. Dual core processor, 4GB RAM = cca. 100 concurrent users per server
2. Quad core processor, 4GB+ RAM = cca. 150 concurrent users per server
3. Quad core (or more), 8GB+ RAM + using Virtual Machines = cca. 300-500 concurrent users per physical server (cca. 150 per virtual machine)

Memory Reguirements

As a rule of thumb, we suggest that you assign 90% of server memory to Thin@. In a 4GB environment that would be about 3.7GB.
However, every Thin@ installation will have its unique requirements, so it is recommended to fine-tune that percentage to your own environment, taking into consideration other memory-consuming applications that are running on a Thin@ Application Server, such as Antivirus software etc.

Processor requirements

For a basic Thin@ server installation, we suggest a dual core processor, for example 2x Xeon 2.5GHz, as the preferred processor configuration for a Thin@ Application Server.
However, for top performance a Quad Core processor(or more) is a better option, depending on the amount of server-side processing that is performed. For example, if you place your Database on a separate server and most of your processing and business logic is held in the database tier, then probably two processor cores will be more than enough. On the other hand, if your business logic processing is made on the Application Server and you have a lot of complex calculations, reports, etc., more processing power is recommended.

How to calculate the memory/processor requirements for your specific configuration?

How to calculate memory requirements?
Calculating the memory requirements is easy: Just start your application and see how much memory it uses in the Windows Task Manager.
Total amount of memory per server = (Application memory * 2 [expected memory growth] * 120 [users per server]) + (OS-related memory + Memory required for other applications)
A standard Clarion application will grow in memory after some time, but not much. It will grow in the following manner: Originally it will take X amount of memory. When you open a window, the memory will increase. When you close the window, used memory will not drop much. When you open again the same window, memory will not increase much. So we could say that the more the application is actively used, the more memory it will occupy. In practice this never exceeds 2x the original memory size.

How to calculate processor requirements?
Processor requirements should be determined by the type of the application you're using. A good approach to this is to monitor processor usage in MS Windows over an extended period of time while an application is being actively used on that machine.

How to monitor Thin@ memory/processor usage in Windows?

Thin@ NetSetup has already an integrated preview of memory used by currently connected users.
There are two ways in which you can monitor processor usage:
The first is to start Task Manager and observe processor usage over time while the application is being actively used on that machine. The result should be in the range of 0.5%-1.5% of single processor usage per application.
The second way is to start Windows Performance Monitor: go to System and Security – Administrative Tools – Performance Monitor.
There you can add various counters, start Data Collector Sets and view Reports. Those reports can give you more accurate information about processor usage, memory usage etc.

Maximum Windows heap size limitation

In the past, Windows Heap Size Limitation was a limiting factor. However, in Windows Server 2003 (64-bit), Windows Server 2008 (23-bit and 64-bit), Windows 7 and Windows Vista this is no longer an issue. For more information on this topic read: ... rview.aspx ... art-2.aspx

On older operating systems, there is a desktop heap limitation which prevents you from opening a large numbers of windows or, in some cases, out of memory errors can occur (see: The desktop heap is basically an array that contains information about opened windows. As the number of opened windows grows, the array gets bigger, and it takes more and more time for a full loop through the array. This internal Windows limitation reduces the maximum number of concurrent users that a Thin@ Server can hold.
You can find more information on how to tweak the Windows Heap Size for older operating systems in our Thin@ Installation Instructions.

Where to host Thin@ Servers?

Mochahost is our recommended virtual hosting company. They offer professional datacenters and great service at relatively low prices. If you decide to host your Thin@ applications on a virtual server, Mochahost can provide you great hosting options. See a list of their Dedicated Virtual Server Hosting Solutions.

Re: Thin@ Application Server Hardware Requirements

Posted: Sat Jun 29, 2013 6:11 am
by siamon

I working on testing out Thin@ 2.2 in an app. I have a couple browses which have a SHEET control with vertical tabs. When the app is run via Thin@ the vertical tabs turn horizontal. I have not yet read what I may need to do to correct this. Any advice or pointers?

Decrease your exam stress by using our latest Pass4sure 640-875. For more information visit our ARM website and Columbia University main page also on University of Central Arkansas best wishes

Re: Thin@ Application Server Hardware Requirements

Posted: Wed Jul 03, 2013 9:33 am
by mgolem
I will test this and if it's really an 2.2 issue (worked in past versions) we will fix it in upcoming build.