Received: by 10.14.96.2 with SMTP id q2mr998400eef.6.1329406033470;
        Thu, 16 Feb 2012 07:27:13 -0800 (PST)
X-BeenThere: redis-db@googlegroups.com
Received: by 10.14.38.22 with SMTP id z22ls599493eea.0.gmail; Thu, 16 Feb 2012
 07:27:09 -0800 (PST)
Received: by 10.14.126.146 with SMTP id b18mr996092eei.8.1329406029483;
        Thu, 16 Feb 2012 07:27:09 -0800 (PST)
Received: by 10.14.126.146 with SMTP id b18mr996090eei.8.1329406029464;
        Thu, 16 Feb 2012 07:27:09 -0800 (PST)
Return-Path: <anti...@gmail.com>
Received: from mail-ey0-f169.google.com (mail-ey0-f169.google.com [209.85.215.169])
        by gmr-mx.google.com with ESMTPS id p49si5034192eef.0.2012.02.16.07.27.09
        (version=TLSv1/SSLv3 cipher=OTHER);
        Thu, 16 Feb 2012 07:27:09 -0800 (PST)
Received-SPF: pass (google.com: domain of anti...@gmail.com designates 209.85.215.169 as permitted sender) client-ip=209.85.215.169;
Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of anti...@gmail.com designates 209.85.215.169 as permitted sender) smtp.mail=anti...@gmail.com; dkim=pass header...@gmail.com
Received: by mail-ey0-f169.google.com with SMTP id g11so767528eaa.28
        for <redis-db@googlegroups.com>; Thu, 16 Feb 2012 07:27:09 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:from:date:message-id:subject:to
         :content-type:content-transfer-encoding;
        bh=cJ/HNuwtOKvimdGzLq8wfV03JH9TgqkpStWK+XQnIAU=;
        b=e7/QVVkMoTidCkdEg2+5r2rlW4JfVhqyfxDAIwJ/sgztTxIsVZzUn/rVYuiNUAh9K+
         jpw6Mz/niNlEuqYVCrExVpSdw2fmf9E6EEsK/tAZLObAjbDZg/vROLLxGee0UU3bCOA0
         zNrJH7Wte1tfdCq12JhlocXkJXWIoU95nKsBQ=
Received: by 10.204.149.198 with SMTP id u6mr1492159bkv.138.1329406029302;
 Thu, 16 Feb 2012 07:27:09 -0800 (PST)
MIME-Version: 1.0
Received: by 10.223.74.195 with HTTP; Thu, 16 Feb 2012 07:26:49 -0800 (PST)
In-Reply-To: <CAH=gea-JWf5=_x3nhar=fBxQyrhCr4oYnySKW=XCFucGisgESg@mail.gmail.com>
References: <CAH=gea-JWf5=_x3nhar=fBxQyrhCr4oYnySKW=XCFucGisg...@mail.gmail.com>
From: Salvatore Sanfilippo <anti...@gmail.com>
Date: Thu, 16 Feb 2012 16:26:49 +0100
Message-ID: <CA+XzkVc_3Vj95+gboAiSBwoo8CcEXTMcwuZThU1DjLGQ=SY...@mail.gmail.com>
Subject: Re: redis 10K connection limit?
To: redis-db@googlegroups.com
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hi, unstable version (2.6 RC1 in a few weeks) does not contain such a
limit at all.
For now you can redefine AE_SETSIZE and recompile.

Cheers,
Salvatore

On Thu, Feb 16, 2012 at 4:25 PM, Michael Gorsuch
<michael.gors...@gmail.com> wrote:
> During some tests yesterday, we noticed that connections would fail
> once we exceeded 10K to a single Redis instance. =A0In our case, we
> really do need to go above that.
>
> I noticed this thread:
>
> https://groups.google.com/group/redis-db/browse_thread/thread/ea1eb5406ce=
077e7?pli=3D1
>
> Can anyone comment on the risks involved with increasing AE_SETSIZE?
> Is the default 10K just an arbitrary limit, or was it put in place for
> specific reasons?
>
> Thanks a lot!
>
> Michael
>
> --
> You received this message because you are subscribed to the Google Groups=
 "Redis DB" group.
> To post to this group, send email to redis-db@googlegroups.com.
> To unsubscribe from this group, send email to redis-db+unsubscribe@google=
groups.com.
> For more options, visit this group at http://groups.google.com/group/redi=
s-db?hl=3Den.
>



--=20
Salvatore 'antirez' Sanfilippo
open source developer - VMware

http://invece.org
"We are what we repeatedly do. Excellence, therefore, is not an act,
but a habit." -- Aristotele