From owner-freebsd-arm@FreeBSD.ORG Wed May 13 15:19:34 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 DED483C7 for ; Wed, 13 May 2015 15:19:34 +0000 (UTC) Received: from mail-pd0-f182.google.com (mail-pd0-f182.google.com [209.85.192.182]) (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 B750F1944 for ; Wed, 13 May 2015 15:19:34 +0000 (UTC) Received: by pdea3 with SMTP id a3so54618020pde.3 for ; Wed, 13 May 2015 08:19:28 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:content-type:mime-version:subject:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to; bh=vd7wp1gaWd8ZxC0m1OR3a4+CvOBVWZWMgY/acEiSHyE=; b=YPJWUx2yEIz4A1VIj7i4+QkDOrEQ3ZH2J4AKuhDJd87I5wyUKcYBVjJSXN/mnKrTJq HjNuWxBkrFJVArYkLj02jAqmG6zvWRJysVOEmSovWB1DpfN+sBaizoj3z1FMLkxA88Xl AI7CjEPEe3WjSXfx3yMPRxtIpXopJCrLUNXjJ665qlyLAsOizq4THEldXgmNIP5aCnhn hv3OuqhthrGsao93jCPZpLFsW54dx0oximMSGdnqZCtc0C8iXSOvyPNzdFZLDqTtfEHw RmWpeaw6WjpmBc2Cm2nYcjpG7NWEGDjjVSSsWklT9cEROAjx70Y+DT9g85uUyembt8DM mEWw== X-Gm-Message-State: ALoCoQnIzhklD8hMEVfjnSFFSWJJwha7FvtYywmL9J5lWM3sE9EHgs58cKmTVwksXP15ylHAIH+v X-Received: by 10.69.31.106 with SMTP id kl10mr37856495pbd.155.1431530368714; Wed, 13 May 2015 08:19:28 -0700 (PDT) Received: from [192.168.1.100] (c-24-6-220-224.hsd1.ca.comcast.net. [24.6.220.224]) by mx.google.com with ESMTPSA id ax2sm19717482pac.21.2015.05.13.08.19.26 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 13 May 2015 08:19:27 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2098\)) Subject: Re: Performance issues with raspberry pi 2 From: Tim Kientzle In-Reply-To: Date: Wed, 13 May 2015 08:19:25 -0700 Cc: freebsd-arm@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <5C015967-4CE2-403E-A0BA-200F8EAA1AC4@kientzle.com> References: To: Andreas Andersson X-Mailer: Apple Mail (2.2098) 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: Wed, 13 May 2015 15:19:35 -0000 Do you have WITNESS and INVARIANTS enabled in your FreeBSD kernel = configuration? WITNESS and INVARIANTS are used on development kernels to enable = additional in-kernel consistency checks. They make things a lot slower = and are normally not enabled in production kernels. If you do have those enabled, try removing them and let us know how much = of a difference it makes. Cheers, Tim > On May 13, 2015, at 4:27 AM, Andreas Andersson = wrote: >=20 > I do understand this is still very new and not ready for "producton" = use. >=20 > But freebsd 11 on rpi2 suffers permance issues. Severely. >=20 > 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. >=20 > On FreeBSD 11 this is at around 85/s. >=20 > 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. >=20 > What information would you need? >=20 >=20 >=20 >=20 > 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. > _______________________________________________ > freebsd-arm@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-arm > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org"