Re: Storing objects in Session Variables - exactly why not?
From: Thomas (me_at_alternize.com)
Date: 03/27/05
- Next message: Sara: ",localhost..."
- Previous message: mjkahn: "Re: ASP stops responding"
- In reply to: Bob Barrows [MVP]: "Re: Storing objects in Session Variables - exactly why not?"
- Next in thread: Bob Barrows [MVP]: "Re: Storing objects in Session Variables - exactly why not?"
- Reply: Bob Barrows [MVP]: "Re: Storing objects in Session Variables - exactly why not?"
- Messages sorted by: [ date ] [ thread ]
Date: Sun, 27 Mar 2005 17:33:11 +0200
> Thanks for the code. I will try it myself sometime.
> Can you share the results of your tests? How much of a difference was
> achieved by using the Session-bound object?
it was roughly in the regions of 20% performance gain. i will defenitely
redo my tests in the near future. the configuration has changed (iis6,
windows2003, new server, new ado). also from what i read here and in your
links, my solution might not be faster anymore in the current environement.
if i can get rid of manual pooling without performance-loss, i'll do this
happily - especially as this would free up ressources.
> PS. Have you at least changed the threading model of your ADO objects by
> using the makfre15.bat batch file which can be found in your ADO folder?
> If you are not using Jet, you really should do this. Most of my objections
> to caching the object in session go away if you change the treading model.
>>
nope. i don't even have this batch file... maybe because in windows2003 mdac
2.8 is already included?
> Would it be too much to ask for you to repeat your tests using
> CreateObject instead of Server.CreateObject?
not at all. i'll prepare some new tests. i always thought it
Server.CreateObject was recommended over CreateObject
> Not only that, but you also may be violating your license agreement for
> your database server. But I am not a lawyer. Just providing some food for
> thought.
honestly, i never clearly understood the licencing of the db server. the
seller sold us a 5-client license of ms-sql server standard. still, does a
5-client-license mean
- 5 different machines connecting to the db-server? - there's only 1 machine
in my setup
- 5 different db-login connecting at the same time to the db-server? - all
my users use the same login
- 5 different connections? - hopefully not. even when you open up the
administration manager, you get more than these numbers of connections...
:-)
cheers,
thomas
- Next message: Sara: ",localhost..."
- Previous message: mjkahn: "Re: ASP stops responding"
- In reply to: Bob Barrows [MVP]: "Re: Storing objects in Session Variables - exactly why not?"
- Next in thread: Bob Barrows [MVP]: "Re: Storing objects in Session Variables - exactly why not?"
- Reply: Bob Barrows [MVP]: "Re: Storing objects in Session Variables - exactly why not?"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
