Return-Path: Delivered-To: apmail-myfaces-users-archive@www.apache.org Received: (qmail 97611 invoked from network); 11 Apr 2011 15:46:03 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 11 Apr 2011 15:46:03 -0000 Received: (qmail 67304 invoked by uid 500); 11 Apr 2011 15:46:02 -0000 Delivered-To: apmail-myfaces-users-archive@myfaces.apache.org Received: (qmail 67268 invoked by uid 500); 11 Apr 2011 15:46:02 -0000 Mailing-List: contact users-help@myfaces.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "MyFaces Discussion" Delivered-To: mailing list users@myfaces.apache.org Received: (qmail 67260 invoked by uid 99); 11 Apr 2011 15:46:02 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 11 Apr 2011 15:46:02 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,RFC_ABUSE_POST,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of mhn4dev@googlemail.com designates 209.85.214.53 as permitted sender) Received: from [209.85.214.53] (HELO mail-bw0-f53.google.com) (209.85.214.53) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 11 Apr 2011 15:45:54 +0000 Received: by bwg12 with SMTP id 12so5172549bwg.12 for ; Mon, 11 Apr 2011 08:45:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:message-id:date:from:user-agent:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=DYY9Df+joDu6H+51kkx8u5EdIp1jLO+FX5su8Idm9DM=; b=RH8iAvtJ7wAWqztnEZfp0fkfEPrfORlqeH6CMHmdN5SfJ2yQDDOxQS3ITgbysq7Dku /oVj+Ja+2Hglpsn4On4Gj58JpTRX4gRiLzwi50UmOmFYYBiuD53aZHIszCvQjKn1qFuA thuf0HiuMURoPNXRShhUUFp8XdjqWWk6s1B3M= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; b=Q1LItvbDv2BwXA79l39X37HaWpqhkNOMViugFix9RmtlWdhEDZpCaZyx4tN66Ds5N3 IYVSgFt/21Xu4ENO8I53Z9r4ichSjHBVLuyjAnBdVQAzW+WbPFI1laMPh1kk9JfD2bf7 bkkcoKuUtcs09M98ahWAWqDrcqcDLovsibWCw= Received: by 10.204.74.21 with SMTP id s21mr3227830bkj.62.1302536734151; Mon, 11 Apr 2011 08:45:34 -0700 (PDT) Received: from [10.55.200.162] ([194.25.214.106]) by mx.google.com with ESMTPS id t1sm3294534bkx.7.2011.04.11.08.45.32 (version=SSLv3 cipher=OTHER); Mon, 11 Apr 2011 08:45:33 -0700 (PDT) Message-ID: <4DA3221B.7000400@googlemail.com> Date: Mon, 11 Apr 2011 17:45:31 +0200 From: Michael Heinen User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.9.2.8) Gecko/20100802 Thunderbird/3.1.2 MIME-Version: 1.0 To: MyFaces Discussion Subject: Re: JSF application very slow with HTTPS References: <301638.65780.qm@web27806.mail.ukl.yahoo.com> In-Reply-To: <301638.65780.qm@web27806.mail.ukl.yahoo.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Fat? Well there is a lot of EL in this table, nearly in all cells, e.g. for column widths, values, styles etc. The EL is always hitting backing beans, some with additional map access. But the real problem is the poor HTTPS performance compared to HTTP. It should not be caused by the app and also not by JSF or Tomcat of course. There should be a little overhead for additional handshaking, but not for the rendering! Could this be caused by a buffering whereever? Mark (or anybody else), did you compare your app with http and https? Just wondering whether this is a problem only in my app. Regards, Michael Am 11.04.2011 17:27, schrieb Mark Struberg: > Btw another question: 1s local response time? How fat is this page? > > We have a really big page in production with 1400 lines in a dataTable - and it renders in 450 ms... > > How many back-and-forth requests do you see if you open firebug? > Do you have some EL involved which isn't hitting the backing bean but directly goes into the database? Something in this direction... > > LieGrue, > strub > > --- On Mon, 4/11/11, Mike Kienenberger wrote: > >> From: Mike Kienenberger >> Subject: Re: JSF application very slow with HTTPS >> To: "MyFaces Discussion" >> Cc: "Michael Heinen" >> Date: Monday, April 11, 2011, 2:20 PM >> I also use >> jetty-6.1.22. My environment is almost >> identical to >> yours, give or take a minor version number. >> >> On Mon, Apr 11, 2011 at 7:49 AM, Michael Heinen >> wrote: >>> Hi, >>> >>> My JSF application is very slow via HTTPS. >>> Some parts are 15 times slower compared to HTTP >>> >>> I measured the response times of the xhtml requests >> with Fiddler (locally >>> and over network) >>> >>> Result for a very large page (512 KB) with a big >> datatable without ajax >>> usage: >>> -- local access with HTTP: 1 sec >>> -- local access with HTTPS: 15-16 sec >>> >>> Other pages are factor 2-4 slower, with or without >> ajax. >>> The time is spent in >> htmlTableRenderer.encodeInnerHtml. Data is of course >>> available, there is no additional backend access. >>> >>> The simple download of xhtml files or other files is >> NOT (noticeable) >>> slower. >>> Other non JSF applications running on the same servers >> are also not slower >>> with HTTPS. >>> >>> Before I start profiling: >>> - Does anybody have an idea where I should look at? >>> - Are there any known JSF or webApp settings that >> influence https >>> performance? >>> >>> Environment: >>> Facelets >>> myFaces 1.2.9 >>> tomahawk12_1.1.10 >>> richfaces 3.3.3 >>> tomcat 6.0.29 >>> jdk 1.6.0_23 >>> >>> Regards, >>> Michael >>>