Open Source Telephony
 help / color / mirror / Atom feed
From: Denis Kenzior <denkenz@gmail.com>
To: ofono@ofono.org
Subject: Re: [RFC 1/1] GPRS Provisioning Plugin.
Date: Wed, 13 Jul 2011 08:18:48 -0500	[thread overview]
Message-ID: <4E1D9B38.3000206@gmail.com> (raw)
In-Reply-To: <4E1D764F.5000707@intel.com>

[-- Attachment #1: Type: text/plain, Size: 1051 bytes --]

Hi Oleg,

On 07/13/2011 05:41 AM, Oleg Zhurakivskyy wrote:
> Hello Denis,
> 
> On 07/08/2011 09:23 PM, Denis Kenzior wrote:
>> What I wonder is what is the overhead of the XML parser right now (e.g.
>> how long it takes on reasonable embedded hardware).  If this takes a
>> while, then it might be better to pre-parse the mobile-provider-info db
>> during plugin initialization and not every time gprs_provision is
>> called.  Otherwise we run the risk of hanging the daemon while the
>> provision settings are being looked up.
> 
> I have tested on N900 (MeeGo 1.2 Community Edition on microSDHC class 4
> card), it takes 0.1 second to load and parse the mobile-provider-info
> database (154KB).
> 
> Is this a reasonable time or should we go with pre-parsing?

My rule of thumb is less than 300 ms is not really noticeable to the
user and anything up to 1 second is OK.  So in this case I'd say we
should be fine parsing on demand.

If we ever encounter performance problems we can revisit this decision.

Regards,
-Denis

      reply	other threads:[~2011-07-13 13:18 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-08 11:33 [RFC 0/1] GPRS Provisioning Plugin Oleg Zhurakivskyy
2011-07-08 11:33 ` [RFC 1/1] " Oleg Zhurakivskyy
2011-07-08 16:55   ` Marcel Holtmann
2011-07-11 12:55     ` Oleg Zhurakivskyy
2011-07-08 18:23   ` Denis Kenzior
2011-07-11  7:47     ` Oleg Zhurakivskyy
2011-07-11  8:11     ` =?unknown-8bit?q?R=C3=A9mi?= Denis-Courmont
2011-07-10 14:23       ` Denis Kenzior
2011-07-13 10:41     ` Oleg Zhurakivskyy
2011-07-13 13:18       ` Denis Kenzior [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4E1D9B38.3000206@gmail.com \
    --to=denkenz@gmail.com \
    --cc=ofono@ofono.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox