On Apr 28, 3:39 pm, egervari <ken.egerv...@gmail.com> wrote:
> I can imagine that these are some very expensive requests. In the java
> world, I can simply put the thesaurus and grammar checker (with rules)
> entirely in memory as Java beans in a spring container. When the app
> starts up, we initialize these two services and they just stay in
> memory, waiting for requests.
>
> When user requests come in that need to use the thesaurus or grammar
> checker, they happen extremely quickly because they are just sitting
> in memory the entire time.
>
> Since Ruby is a scripted language, does that mean this would not be
> possible?
Does sound to me like this would be a problem - it's entirely possible
to set something like this up during app startup.
The only issue you might have is that (unless you go down the jruby
world) with ruby you'd have multiple rails application processes (MRI
never runs more than one thread at once), and so each one would have a
copy of this thesaurus, you might end up using a lot of memory
Fred
Fred
> Would there be a way to make these extremely performant
> using the Rails paradigm? Or is this a bad fit for Ruby and Rails?
>
> Thank you.
--
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
To post to this group, send email to rubyonrails-talk@googlegroups.com.
To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
No comments:
Post a Comment