What is the size limit of an application object in classic asp?

Question

I am creating an ASP script that uses an application object to store pages. The question, in my opinion, is whether there is a size limit for this object. Somebody knows?

Answer 1

An application pool can determine the maximum size of virtual memory that a workflow can allocate. This parameter affects the maximum data size that the application object can hold.

If this parameter is not specified (or exceeds 2 GB), then another factor will be whether the process is running in 32-bit mode. If so, you can only expect to get a maximum of 1.5 GB (if it is) in the application, no matter how much memory is present on the server.

On a 64-bit server executing a workflow as a 64-bit process, it will be able to consume as much RAM and a page file that it can receive.

Answer 2

I am sure that there is no obvious restriction, but, of course, at some point you will use so much memory that you will see other effects - for example. Your application is being processed because it has exceeded the memory limit, or your application stops because the server runs out of memory.

Answer 3

I am sure that the limit is indeed the RAM of the hosting server. If you have a very large number of pages, it is useful to use a database or files for pages with less accessible access, but I have never seen any specific problems with a hard limit.