Skip to content
This repository was archived by the owner on Apr 17, 2018. It is now read-only.
This repository was archived by the owner on Apr 17, 2018. It is now read-only.

Unexpected Connection Pooling #6

@TonsOfFun

Description

@TonsOfFun

Hi,

I am using Puma, Sinatra, and dm-postgres-adapter with the following configuration. I am posting this issue on both Puma and dm-postgres-adapter.

  configure do
    enable :logging
    DataMapper.setup(:default, {
      adapter: 'postgres',
      host: 'localhost',
      pool: 5,
      database: 'my_app_development'
    })
    DataMapper.finalize
    DataMapper.auto_upgrade!
  end

This configuration has erratic connection behavior. If I the fix the threads in Puma to 2:2 under load I get 5 connections, with 4:4 I get 6 connections, and the default 0:16 uses 13 connections.

I am using siege -c 100 -r 10. What is the expected behavior here?

Thanks.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions