long-running

However, the best performance doesn't kick in until the JVM is sufficiently warmed up, which means JRuby shines mostly for long-running tasks.

Biggest long-running tech companies had positive revenue since very early in their life (if not day 1).

For compute bound tasks, it is often productive to split computations into long-running processes.

Most of them have policies of automatically killing long-running processes even nowadays.

This has the advantage that I can start long-running jobs that persist on the server even as I'm moving between locations.

JRuby is optimized for production-level long-running workloads.

But --dev is good stuff - it basically turns off the JIT and invokedynamic, which are great for long-running processes but not that useful for shorter script runs or consoles.

It sounds a little bit to me like you're re-inventing the wheel - multi-threading means you don't have to go to the pains of breaking your long-running tasks up into pieces, the infrastructure takes care of that for you.

As noted in the article, there's a long-running problem with confusing the FSF's preferred interpretation of the interaction between copyright law and the GPL's wording with the reality of how copyright law would interact with the GPL's wording, especially on the matter of what does or does not constitute a derivative work of a piece of software.

But benchmarks consist of running the same code repeatedly in a long-running loop, which encourages development of sophisticated, highly-optimizing JITs that spend a lot of time in up-front compilation, which end up being totally pointless for JS whose sole purpose is to run once to place an ad somewhere on the page.

Maybe my app is more complicated, and I have some type of long-running job, so I create a job class with all the job parameters, and stick it in Session, Redis, or plain App Memory Cache, while the client polls to see if the job is complete.

JRuby defaults to "good for long-running processes" mode, which is great for production but less useful when running short-lived tasks.

There are some long-running “batch-jobs” for large computations where it’s acceptable to apply a response retroactively, but most uses of Sigma are synchronous—a client needs to know immediately (more or less) how some bit of content is classified and what action to take in response to it.