Dictionary / Client VS. Application variables

Hi, I asked a question about the performance of my server ... I have a classic asp cms hosting ~ 250 sites, for each site we create a classic ASP dictionary using

set dict = CreateObject("Scripting.Dictionary") 
dict.add "test1","Value Test1"
dict.add "test2","Value Test2"
dict.add "test3","Value Test3"

this dictionary is then loaded onto each page for each user ...

let's say we got about 150,000 users visiting these websites, monthly downloading this dictionary about ~ 100 thousand each each load ...

Should I use the application variable as a dictionary, and not load my dictionary every time?

and will it really improve my server performance?

+5
source share
3 answers

, ASP , .

- , , , - .

. . ? , .

+2

, Dictionary , : , , , , , , , ( "" ). ...

, - , - ( ) , (, ).

+1

, -. , , , . , , - 100 , .

We are launching a classic ASP site that processes 200,000 page views per day and makes extensive use of scriping.dictionary on each page (25+ copies). We use it as the basis for all kinds of things. Do you have an example script to show that a dict is not always destroyed by garbagecollector? Or is the search slow compared to any alternative? The only inconvenience we encountered was the lack of a “clone” method.

+1
source