JT ArchieJT Archie
Standup 08/26/2010 - Rails controls too much of cache
edit Posted by JT Archie on Thursday August 26, 2010 at 09:17AM

Help

"Does Postgres have an equivalent MySql Myisam high write performance?"

A Pivot was wondering what settings in Postgres can be enabled for high performance INSERTs (willing to sacrafice SELECT performance on said table).

"Why is Paperclip giving a Stream close error when in development?"

When using Paperclip in development, any file upload results in a Stream IOError. Trying to replicate the problem with Paperclip on its own causes no problems, so it appears to be a conflicting library.

Interesting Things

  • An update to yesterday's Rubymine font size issue. The file drawer can not be specifically updated, but the overall system font can be under Preferences > Appearance > Fontsize. Make sure to restart Rubymine.
  • Google Voice has been added as a service on to GMail. Make phone calls for free to anywhere in the US from your browser.
  • An update to yesterday's Safari 'Back' button issue. Safari caches the previous ajax call (dubbed ajax zombie) when going back to a previous page. The fix had to do with changing Rails default "Cache-control" header to be "no-store".

Comments

  1. Joseph Palermo Joseph Palermo on August 26, 2010 at 03:35PM

    I don't have a solution for Postgres, but this article is about scaling writes in MySql (MyISAM is not the answer btw).

    http://tech.bluesmoon.info/2009/09/scaling-writes-in-mysql.html

  2. Miho Miho on August 26, 2010 at 09:48PM

    Does Postgres have an equivalent MySql Myisam high write performance?

    Not exactly sure what MySQL MyISAM high write performance referred to ... but some tips about PostgreSQL:

    A. Use COPY command instead of INSERT command B. Drop any indexes or constraints (then re-create them after data load) C. Up checkpoint_segments config value

  3. Miho Miho on August 26, 2010 at 10:02PM

    Hmm.. in my previous comment, my precious carriage returns were ignored...

    Hoping this time it's bit more readable by adding blank lines in between:

    A. Use COPY command instead of INSERT command

    B. Drop any indexes or constraints (then re-create them after data load)

    C. Up checkpoint_segments config value