Re: Questions about Heroku Scheduler

Followup questions relating to question #2: 2.1) In the scenario addressed in question 2 below, would the two tasks run in the same dyno, or does Heroku spin up another dyno for the second task? I thought I had read that the scheduled task would allocate dynos from the pool of dynos allocated

Re: Questions about Heroku Scheduler

Re: 2.1, what happens when running on Bamboo? On Mar 8, 2012, at 4:04 PM, Jack Royal-Gordon wrote: > Followup questions relating to question #2: > > 2.1) In the scenario addressed in question 2 below, would the two tasks run > in the same dyno, or does Heroku spin up another

Increasing Availability

Tonight's Amazon outage taking much of Heroku down for several hours (second time in as many weeks) has left me with two fundamental questions: 1) What is Heroku doing to make their architecture more available, such that their control surfaces are less sensitive to localized Amazon outages? I g

Re: Digest for heroku@googlegroups.com - 1 Message in 1 Topic

We've used it very lightly, but have had no problem with jobs just hanging. We do occasionally have jobs that fail and get retried, but nothing has gotten "stuck" (and the job failure is certainly no DJ's fault). But if I were you, I'd want to hear from someone using it more heavily than we ar

Re: Digest for heroku@googlegroups.com - 1 Message in 1 Topic

We faced the same issue, wanting to improve the efficiency of a long-running web scraper running as a worker on Heroku. After looking at the available options (including EventMachine, which is clearly a good product), we chose to use Sidekiq. Sidekiq multi-threads tasks within a single worker

Controlling when Automatic PG Backups are Taken

When I first setup my app to use PG Backups, it was taking backups at 11am local time (exactly when I wanted it to). Apparently, since my database was migrated, it reset the backup time to 11pm local time (when the background portion of my app is very busy updating the database. As a result, t

Logs seem awfully big

I'm using LogEntries to store my sys logs, but I'm apparently generating a very large log volume (~87GB/~270M events per day). My app has relatively few users (100) who use it very lightly (16,665 HTTP Requests per day). The main cause seems to be that my inserts can be very large (including w

ArgumentError when starting Unicorn on Heroku

Switched my RoR (3.1.3, 1.9.2, Cedar Platform) app from Thin to Unicorn (4.6.2). It ran fine in development (Mac OSX), but when deploying to production on Heroku, it fails with the following messages: Starting process with command `bundle exec unicorn start -p 6069 -c ./config/unicorn.rb` /

Out of Memory Errors on Simple Queries that Worked Previously

Tonight, I started getting "out of memory" errors from several different queries, many of which are simple, and all of which have worked well in the past. For example, a simple "select" across several hundred rows that should produce 20 rows or less gets this error. App has not been touched in

Re: Out of Memory Errors on Simple Queries that Worked Previously

n Simple Queries that Worked Previously > Jack Royal-Gordon May 29 11:47PM -0700 > > Tonight, I started getting "out of memory" errors from several different > queries, many of which are simple, and all of which have worked well in the > past. For example, a si

"Fixing nokogiri install" message during Slug Compilation

I noticed the following message in my Heroku build log today: "Fixing nokogiri install. Clearing bundler cache." and the build took much longer as it had to install all my gems instead of using them. What does this mean to my app? -- -- You received this message because you are subscribed to

Headless Processing on Heroku

I'm trying to scrape some websites that rely on Javascript, so I found this article discussing Watir and headless processing. I ran into the following exception: Headless::Exception: Xvfb not found on your system. So I started researching Xvfb and discovered that it is a stand-alone display se

Letting the pager solve R14 Errors

I have background processes running Sidekiq that run for several hours each night. They generate a large number of R14 errors (1600 for 2 processes each running about 6-9 hours). But it seems like the excessive memory is slight (not more than 520MB vs the 512MB allocated), so it would not be j

Read/Write Sharding with Heroku Postgres

I have an application that has a little db updating in the foreground (mostly user configuration), and a great deal of db updating in the background (scraping information off the web for 12 hours per day). I'm starting to see the performance of the foreground web requests be affected by the back

Re: Digest for heroku@googlegroups.com - 3 updates in 2 topics

You can start here: https://devcenter.heroku.com/articles/platform-api-reference > On Jun 27, 2018, at 3:35 AM, heroku@googlegroups.com wrote: > > heroku@googlegroups.com > > Google Groups >