Ruby on Rails Thursday, June 22, 2017

Thanks Dave, I'll look into the "Nice" utility you mentioned -- I'm currently unfamiliar with it.  Also traffic on the application isn't heavy as its only used on an internal network for roughly 60 users at the moment. However, I would prefer to find the "correct" way of doing it.  I'm thinking I may resort to using another machine, but at the moment I don't have those resources.  Rails is the only thing on the server right now... so that helps as well.  With some of the PDFs that time several minutes to run, we have seen a slow-down for other users accessing pages.  Since the PDF generation isn't urgent I don't mind having it last longer as long as it doesn't slow down the rest of the application for the other active users.  Thanks again for the "Nice" recommendation I'll be looking into it shortly.

On Thursday, June 22, 2017 at 12:51:59 PM UTC-4, Dave Aronson wrote:
On Thu, Jun 22, 2017 at 12:08 PM, David McDonald <> wrote:

> when I generate
> a PDF files, usually the CPU will get to ~80+% during the generation

Ouch!  The big question is: are you actually doing anything else with
that server?  If Rails has the machine all to itself, and you don't
have enough traffic that someone else is probably waiting for a reply,
you may be OK as-is.

Otherwise, a number of other approaches come to mind.  As you
mentioned, you could put it on another machine.  You could also see if
you could "nice down" that process, i.e., use the "nice" utility (or
some such programming) to set the priority of the PDF-making process
so that others can have a better share.


Dave Aronson, consulting software developer of,,, and

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
To post to this group, send email to
To view this discussion on the web visit
For more options, visit

No comments:

Post a Comment