From owner-freebsd-arm@FreeBSD.ORG Thu May 14 06:39:37 2015 Return-Path: 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 C7D6F39D for ; Thu, 14 May 2015 06:39:37 +0000 (UTC) Received: from mail-ig0-f173.google.com (mail-ig0-f173.google.com [209.85.213.173]) (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 98F451361 for ; Thu, 14 May 2015 06:39:36 +0000 (UTC) Received: by igbhj9 with SMTP id hj9so65293161igb.1 for ; Wed, 13 May 2015 23:39:30 -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:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=/3+SoCz/Hwc03c2wlPM4JWEK7RKJkCyuCu8HPmwLpb4=; b=iRnsSz3IT0/TIEqp06tMu2AQYUTuWi4Z1kN8RNzjkKc9YKIhsxDepyfHuZ3ef80CsA boX6WHPl7fL+L0FNI3Z7TEUKPfxk2NJ8oS2Y2gw606bLXH3LVP6786RWkp8UYvgRE6ci E2WxpkcMMUD6eqTwYRnEPWtfqvB0EOCBrcpVUBsSecggKgVxrYlyJ6ocAffUQVzMe3Ty fg02/ahBs0Bihwxl2Dfv5ppB4P/aOeENgjuWfbfieoaYXiG3FydL5OQPYYeYZX8u6fyZ AuYoXRovOND3K75ha73GH9d71BxAxoc8Pb+9jehCISczyd88IyfdekNckH9/M9B+Qz1Z sJJg== X-Gm-Message-State: ALoCoQmcD2ndULQau3dF2RSu9arKdhUqfWY3Wc6rKLpZYpfzaL3C7FkoOUpUaGx6FoPVtamo9OsL MIME-Version: 1.0 X-Received: by 10.107.129.91 with SMTP id c88mr3371471iod.81.1431585570082; Wed, 13 May 2015 23:39:30 -0700 (PDT) Received: by 10.36.28.201 with HTTP; Wed, 13 May 2015 23:39:30 -0700 (PDT) In-Reply-To: <1EE88AD4-2B4A-496B-9366-7F9A89F57D6D@bsdimp.com> References: <1EE88AD4-2B4A-496B-9366-7F9A89F57D6D@bsdimp.com> Date: Thu, 14 May 2015 08:39:30 +0200 Message-ID: Subject: Re: Performance issues with raspberry pi 2 From: Andreas Andersson To: Warner Losh Cc: freebsd-arm@freebsd.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable 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." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 May 2015 06:39:37 -0000 Just built an image for the raspberry pi without the witness options.. Will try to build with TARGET_ARCH=3Darmv6hf later on. Eager to test the performance of tornadoweb on the rpi first. :) Will come back with benchmarks later. What else would be nice to benchmark? Is there a standard set of benchmarks that I can run and provide results for? 2015-05-13 17:04 GMT+02:00 Warner Losh : > > > On May 13, 2015, at 5:27 AM, Andreas Andersson > wrote: > > > > I do understand this is still very new and not ready for "producton" us= e. > > > > 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 softwa= re > > floating point, while on raspbian we are doing stuff with hardware > floating > > point. > > FreeBSD is still using soft float. We=E2=80=99ll be transitioning that to= hard > float > for 11.0, and should have the code for that pushed into head by the end > of BSDCan 2015. > > In the mean time, you can try building an image with TARGET_ARCH=3Darmv6h= f > to see if that is the cause of the problems. > > Warner > > >