On Sat, Dec 31, 2005 at 04:34:32PM -0800, Cliff Wells wrote:
> 
> Kevin Dangoor wrote:
> >On 12/31/05, Davide Bertola <[EMAIL PROTECTED]> wrote:
> >  
> >>The same page with the same template
> >>takes 0.4/0.5 seconds more if you are a logged user.
> >>    
> >
> >That's a big difference! I don't know how it could take that much longer.
> >
> >  
> >>For an unlogged user the whole page tales 0.2 sec
> >>and it uses the database more than identity may need.
> >>
> >>You can see that if I'm online : http://dade.ath.cx:8080/
> >>refreshing many times and logging with "foo"/"bar"
> >>
> >>(Powerbook G4 1ghz, sqlite database)
> >>    
> >
> >Hmm.... I remember Jeff saying something about identity updating a
> >table. sqlite locks the whole database when anything is being updated.
> >(And, on the Mac, it waits for a full sync before releasing the lock.)
> >I wonder if something like that is going on: your request goes in,
> >database is getting updated, image tries to load but database is
> >locked, it waits, etc...
> >I wouldn't expect an update on *every* hit though.
> >  
> Actually, watching my postgresql logs, it does seem to do an update every hit:
> 
> 
> LOG:  statement: BEGIN; SET TRANSACTION ISOLATION LEVEL SERIALIZABLE
> LOG:  statement: SELECT id, user_id, expiry, value FROM tg_secret_token WHERE 
> user_id = 'username'
> LOG:  statement: UPDATE tg_secret_token SET expiry = '2005-12-31 01:48:49' 
> WHERE id = 2
> LOG:  statement: SELECT id, user_id, email_address, display_name, password, 
> created FROM tg_user WHERE user_id = 'username'
> LOG:  statement: SELECT group_id FROM tg_user_group WHERE user_id = 1
> LOG:  statement: SELECT group_id, display_name, created FROM tg_group WHERE 
> id = 1
> LOG:  statement: SELECT group_id FROM tg_user_group WHERE user_id = 1
> LOG:  statement: SELECT permission_id FROM tg_group_permission WHERE group_id 
> = 1
> LOG:  statement: SELECT permission_id, description FROM tg_permission WHERE 
> id = 1
> LOG:  statement: END

My understanding was that (after a recent change), it set the expiry date
in the db.  Because of this you have to update the expiry date on every
request.

Jason

-- 
If you understand, things are just as they are.  If you do not understand,
things are just as they are.

Attachment: pgp2rFbLBLoTW.pgp
Description: PGP signature

Reply via email to