You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
1.9.3p125 :002 > Response.all.size
Response Load (2908.1ms) SELECT "responses".* FROM "responses"
EXPLAIN (34.5ms) EXPLAIN SELECT "responses".* FROM "responses"
EXPLAIN for: SELECT "responses".* FROM "responses"
QUERY PLAN
------------------------------------------------------------------
Seq Scan on responses (cost=0.00..5622.13 rows=284213 width=47)
(1 row)
=> 284213
There's nothing fancy here yet it took 3 hours to process 250k objects saved.
Is this what it usually takes? If this is the case this gem looks totally inviable for production with not-so-much data stored. In the case of a real problem that would require i.e. restoring a production db based on a local copy it can take literally days over - let's say - a 1GB database.
I'm not sure if I'm missing something obvious here.
heroku db:push and pull will soon be replaced with pg:push and pull, which won't use taps, so it wouldn't have this problem. It'll have all of its own, new problems! If you want a preview check out heroku/heroku-pg-extras#42
I published this question in Stackoverflow, but maybe is more appropriate here
http://stackoverflow.com/questions/10853085/taps-gem-is-slow
The text was updated successfully, but these errors were encountered: