Friday, September 25, 2015
I am now refactoring and optimizing my code and noticed that the calls to update last_activity_at varies between 50 and 100 ms.
I think is is too much to be ok för a simple update.
Have others different or the same experience of sorcery ?
My user table has 6000 rows and 36 fields. (too many - should be refactored anyhow).
Can the slow response times depend on this table, sorcery, the server or the rest of application
What is wrong ?
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-talk+unsubscribe@googlegroups.com.
To post to this group, send email to rubyonrails-talk@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/1e57391f-fe96-47ec-ae56-ab918ae75a1f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment