Homo-Adminus Blog - Latest Comments in FastSessions Rails Plugin Released

Re: FastSessions Rails Plugin Released

Andrew Watkins — Fri, 11 Jul 2008 22:17:33 -0000

We're using postgresql and actually ported it over, except for one problem: Postgresql does have crc32 as a function. You can kind of get there by either writing your own or installing the one with ltree. Postgresql does however have md5. What we did is setup tests against unique(md5_session_string, session_id), unique(crc32, session_id), and unique(md5_session_byte,session_id). The last one is a byte representation of the md5 hash. For random queries, the 1st two implementations ran at about the same speed, which was basically instantaneous. The byte one definitely showed a little lag, and so would not recommend it. Finally we created a stored procedure to actually handle the insert/update as postgresql doesn't have a "ON DUPLICATE KEY UPDATE". The question is whether or not this is faster than just indexing the session_id itself or is something screwy is going on where postgresql is optimizing against the hashed values.

Re: FastSessions Rails Plugin Released

Paolo Montrasio — Thu, 15 May 2008 06:51:29 -0000

There is a plugin called SmartSessionStore that does more or less the same and works also with PostgreSQL. I've been using it for almost an year in production with no problems at all.

Re: FastSessions Rails Plugin Released

Eric — Wed, 02 Apr 2008 13:22:33 -0000

What would the impact be for using fast_sessions with MySQL and MyISAM tables as opposed to InnoDB (table vs. row level locking)? Any thoughts?

Re: FastSessions Rails Plugin Released

Eric — Fri, 28 Mar 2008 16:39:50 -0000

What about using MyISAM for the sessions table. Implications, like for instance, table locking during updates/additions?
Unfortunately, my MySQL database was not compiled with InnoDB.

Re: FastSessions Rails Plugin Released

Andrey — Thu, 28 Feb 2008 05:31:53 -0000

Of course, it's a little bit artificial case, but when session size exceed 70kb I become error (code 500). Log says that sql connection lost during update operation.
After that application don't get back alive, until I delete session record.

Re: FastSessions Rails Plugin Released

Drew Blas — Fri, 22 Feb 2008 10:42:09 -0000

You mentioned turning off sessions from bot requests, but didn't mention how. Here's my method:

[application.rb]
# turn off sessions if this is a request from a robot
session :off, :if => proc { |request| request.user_agentuser_agent =~ /\b(Baidu|Gigabot|Googlebot|libwww-perl|lwp-trivial|msnbot|SiteUptime|Slurp|WordPress|ZIBB|ZyBorg)\b/i }

Re: FastSessions Rails Plugin Released

Matthias — Tue, 19 Feb 2008 07:21:04 -0000

< UNIX_TIMESTAMP(NOW()) - #{seconds}"

Note the UNIX_TIMESTAMP around (updated_at) in first part of the comment

Re: FastSessions Rails Plugin Released

Matthias — Tue, 19 Feb 2008 07:19:53 -0000

the self.delete_old! method did not work for me. I changed it to:

@@connection.execute "DELETE FROM #{table_name} WHERE UNIX_TIMESTAMP(updated_at)

Re: FastSessions Rails Plugin Released

Chris — Thu, 14 Feb 2008 00:51:06 -0000

Why don't you just use the cookiestore in rails 2.0? That way you don't need to store sessions in the database at all!

Re: FastSessions Rails Plugin Released

Ivan V. — Wed, 13 Feb 2008 15:38:26 -0000

I'm no expert at all on databases, but I'll see what I can do :)

Re: FastSessions Rails Plugin Released

Scoundrel — Wed, 13 Feb 2008 14:02:53 -0000

I do not work with postgres, but patches are welcome :-)

Re: FastSessions Rails Plugin Released

Ivan V. — Tue, 12 Feb 2008 19:42:06 -0000

So, this plugin only works with MySQL right? Are you considering supporting other DBs, like postgresql?

Thanks.