Return-Path: X-Original-To: apmail-flex-issues-archive@minotaur.apache.org Delivered-To: apmail-flex-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 12943C7D2 for ; Sun, 3 Nov 2013 23:45:18 +0000 (UTC) Received: (qmail 51356 invoked by uid 500); 3 Nov 2013 23:45:18 -0000 Delivered-To: apmail-flex-issues-archive@flex.apache.org Received: (qmail 51332 invoked by uid 500); 3 Nov 2013 23:45:18 -0000 Mailing-List: contact issues-help@flex.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@flex.apache.org Delivered-To: mailing list issues@flex.apache.org Received: (qmail 51324 invoked by uid 99); 3 Nov 2013 23:45:18 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 03 Nov 2013 23:45:18 +0000 Date: Sun, 3 Nov 2013 23:45:17 +0000 (UTC) From: "Maurice Amsellem (JIRA)" To: issues@flex.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Comment Edited] (FLEX-33865) ConstraintLayout / LayoutElementHelper are memory inefficient (and slow) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/FLEX-33865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13812518#comment-13812518 ] Maurice Amsellem edited comment on FLEX-33865 at 11/3/13 11:45 PM: ------------------------------------------------------------------- Benoit wrote: >Note that it's hard to compare the memory allocation ios / desktop due to really poor optimizations when compiled for ios. So, let's focus on speed optimization, which is more a concern on mobile than memory, right ? Regarding the benchmarks, I suggest you compare typical tasks take make heavy use of layout constraints, such as Form display, or anything else that you find appropriate,from the end user perspective. eg. measure the time to display a form-based dialog box with an without the optimization. That way, we have something "factual" to detemrine if the optimization is worth it. was (Author: mamsellem): Benoit wrote: >Note that it's hard to compare the memory allocation ios / desktop due to really poor optimizations when compiled for ios. So, let's focus on speed optimization, which is more a concern on mobile than memory, right ? Regarding the benchmarks, I suggest you compare typical tasks take make heavy use of layout constraints, such as Form display, or anything else that you find appropriate,from the end user perspective. eg. measure the time to display a dialog box with an without the optimization. That way, we have something "factual" to detemrine if the optimization is worth it. > ConstraintLayout / LayoutElementHelper are memory inefficient (and slow) > ------------------------------------------------------------------------ > > Key: FLEX-33865 > URL: https://issues.apache.org/jira/browse/FLEX-33865 > Project: Apache Flex > Issue Type: Improvement > Components: Mobile: Performance, Spark: Layout > Affects Versions: Apache Flex 4.11.0 > Environment: mobile desktop > Reporter: Benoit Wiart > Assignee: Maurice Amsellem > Labels: mobile, performance > Attachments: 0001-ConstraintLayout-optimizationsV2.patch, layout-1-desktop-memory.png, layout-2-desktop-memory.png > > > ConstraintLayout / LayoutElementHelper are doing too many memory allocation. > it's really bad on mobile > the attached screenshots were taken on desktop -- This message was sent by Atlassian JIRA (v6.1#6144)