From owner-freebsd-arm@FreeBSD.ORG  Wed May 13 11:27:41 2015
Return-Path: <owner-freebsd-arm@FreeBSD.ORG>
Delivered-To: freebsd-arm@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id ECB56F1F
 for <freebsd-arm@freebsd.org>; Wed, 13 May 2015 11:27:41 +0000 (UTC)
Received: from mail-ig0-f176.google.com (mail-ig0-f176.google.com
 [209.85.213.176])
 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
 (Client CN "smtp.gmail.com",
 Issuer "Google Internet Authority G2" (verified OK))
 by mx1.freebsd.org (Postfix) with ESMTPS id C0F9818AC
 for <freebsd-arm@freebsd.org>; Wed, 13 May 2015 11:27:41 +0000 (UTC)
Received: by igbyr2 with SMTP id yr2so135585325igb.0
 for <freebsd-arm@freebsd.org>; Wed, 13 May 2015 04:27:35 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20130820;
 h=x-gm-message-state:mime-version:date:message-id:subject:from:to
 :content-type;
 bh=XtmMn/Bp8aucVImLByz1HiyHOxK00Nfs1s3Lk/MI1Yg=;
 b=gOJ+023lMKgGcrDuUJ9QW5B5FS+aN7jYasQQK9gDFl1C7zQrEQufQxk+x7OZ943WmL
 yVw/vynNNYr6SyNbNNreQo1YQqj46+qvZTB9HxD+Npa71RNXFVQtvksKdAwqyt5r6Kxo
 4eAnGOD44EI+p0i2H8bqYfotSYEUWG7E3Jze6hS76rX3GDgKl60J1K82FLEVTk8kX5/e
 w9mZOz+ASvCtQIsX0qqUVlaJaDywMpOHkkOvCgFbqAuLWGtT7EMPUS/YxML/9Rx0XRMr
 4XZGv4gxLgtZCtgqZkOQTZJVqcgX05e9HdsWi3RY04F0cKslPk666y8LQ3CsAH2A6aIv
 V1Vg==
X-Gm-Message-State: ALoCoQnaRwf55lRxr2CuiKBA/Lozfd3KQ7XIo2sY7TPP4ABHc/HRA9XgTGkWp2ht6HDmNTPKdEPd
MIME-Version: 1.0
X-Received: by 10.42.204.14 with SMTP id fk14mr8253718icb.96.1431516454924;
 Wed, 13 May 2015 04:27:34 -0700 (PDT)
Received: by 10.36.28.201 with HTTP; Wed, 13 May 2015 04:27:34 -0700 (PDT)
Date: Wed, 13 May 2015 13:27:34 +0200
Message-ID: <CAOx9_ZiUw5nkBK=Bsumb=K2W1hv0P+NAwT7OXE7VAz_96awqOw@mail.gmail.com>
Subject: Performance issues with raspberry pi 2
From: Andreas Andersson <aandersson@tappsi.co>
To: freebsd-arm@freebsd.org
Content-Type: text/plain; charset=UTF-8
X-Content-Filtered-By: Mailman/MimeDel 2.1.20
X-BeenThere: freebsd-arm@freebsd.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: "Porting FreeBSD to ARM processors." <freebsd-arm.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-arm>,
 <mailto:freebsd-arm-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-arm/>
List-Post: <mailto:freebsd-arm@freebsd.org>
List-Help: <mailto:freebsd-arm-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-arm>,
 <mailto:freebsd-arm-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 13 May 2015 11:27:42 -0000

I do understand this is still very new and not ready for "producton" use.

But freebsd 11 on rpi2 suffers permance issues. Severely.

For instance, the same code I am running (tornado project which inserts
stuff to rabbitmq) is running at ~190 req/s or 190 publishments/sec (to
rabbitmq) on raspbian.

On FreeBSD 11 this is at around 85/s.

With my consumer (using all the cores) I am seeing a high get rate from
rabbitmq. But ACKing those messages are painstakingly behind. How can I
help you debug this.

What information would you need?




My own theory on this is that on FreeBSD we are doing stuff with software
floating point, while on raspbian we are doing stuff with hardware floating
point.