> On Apr 2, 2015, at 11:29 AM, Jason Fleetwood-Boldt <t...@datatravels.com> > wrote: > >> >> On Apr 2, 2015, at 2:18 PM, Gary Tsai <gary.m.t...@gmail.com >> <mailto:gary.m.t...@gmail.com>> wrote: >> >> Thanks for the reply Jason, >> >> Yea the ticket is currently in Heroku Support - I’m not sure how helpful >> they are - haven’t heard a response yet. I actually tested this against my >> clients production app (it’s paid) so there can’t be anything wrong with the >> service itself terms of a 10,000 rows limit I’ve received before. >> >> Can you explain more about why the runner would have “max memory on it’s >> ‘headless’ runner dyno” >> > > I’m not actually sure exactly what you get with a headless running, but keep > in mind that you have either 1X, 2X, or PX dynos so there must be a > corresponding memory allocation for the headless runner. > > I’m just talking about the memory on the dyno — RAM — once it runs out, the > platform kills it. There isn’t much you can do about that. > > >> It can’t be a memory issue because I tested the upload with only one row. >> > > Indeed, then it sounds like a different problem. Maybe your approach is > wrong? I don’t understand if the file you are uploading is local or if it is > on the app? >
So in the runner I’m actually calling the csv file locally from my desktop. I’ve seen snytax where they keep it in a tmp folder locally on the desktop? I’ve also seen people keep their cvs files in the db folder, and running something like, “heroku rails runner db/your_file.csv” (<——not sure about the command or syntax there) Overall, I just find it strange the rails runner works locally, but not on heroku (still at the WTF - stage). > Perhaps Heroku is detecting your code try to make a disk call and killing it > for security purposes? It definitely looks like it is killed by the platform. > Maybe? > >> I haven’t tried a rake task, but would it be any different? > > > What I do in my app is save the CSV files to a Paperclip object, which gets > saved to an Amazon S3 bucket. The CSV import job (which runs in a worker job, > not a rake task or runner), first downloads a copy of the CSV and saves it to > /tmp (this is safe even in the disk-less Heroku environment because I don’t > rely on this file being there again in the future). Once saved, I then read > the CSV file into memory and process it. > > Heroku support is usually pretty good, depending on the issue. Seems like > either a platform limitation or some other platform-imposed security blocker > that you are seeing. > > -Jason > > -- > -- > You received this message because you are subscribed to the Google > Groups "Heroku" group. > > To unsubscribe from this group, send email to > heroku+unsubscr...@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/heroku?hl=en_US?hl=en > <http://groups.google.com/group/heroku?hl=en_US?hl=en> > > --- > You received this message because you are subscribed to a topic in the Google > Groups "Heroku Community" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/heroku/UNhif0CoY8Q/unsubscribe > <https://groups.google.com/d/topic/heroku/UNhif0CoY8Q/unsubscribe>. > To unsubscribe from this group and all its topics, send an email to > heroku+unsubscr...@googlegroups.com > <mailto:heroku+unsubscr...@googlegroups.com>. > For more options, visit https://groups.google.com/d/optout > <https://groups.google.com/d/optout>. -- -- You received this message because you are subscribed to the Google Groups "Heroku" group. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/heroku?hl=en_US?hl=en --- You received this message because you are subscribed to the Google Groups "Heroku Community" group. To unsubscribe from this group and stop receiving emails from it, send an email to heroku+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
