× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Kevin,

I'd be curious what these times mean. Are you extracting data or is it
simply a process that parses the JSON and puts in into memory? I only ask
because parsing can be different than parsing and retrieving many objects.

A practical example I'd be interested in (as far as speed goes between the
two) is how long it takes to extract a few elements from the sample JSON.

The sample JSON provided is a large array of objects. I'd like too see
times (and maybe sample code) to parse out and retrieve for each JSON array
element:

- each "guid" object
- each "favoriteFruit" object
- the 3rd "tag" for each object
- the 2nd "friends name" for each object.

The reason is a while back I had to write my own JSON parsing routine. At
first is was just a ham-fisted brute force method. :)

Now I'm almost done with an update that makes it exponentially faster
simply because I'm caching object nodes in memory once they're "found" (for
example, running the above example on my little 515 resulted in times 8
times faster after adding the node caching).

I thought about going through the entire JSON file first and storing the
location of each node as well (instead of only storing it when it's
requested and found), but I'm having a hard time convincing myself that's a
good idea since we won't always want to go through the entire JSON file or
need each node's data. But, it's on my "to do" list for improving my
personal JSON parser, or at least for experimentation.

Brad
www.bvstools.com

On Mon, Jun 1, 2015 at 12:12 PM, Kevin Turner <
kevin.turner@xxxxxxxxxxxxxxxxxxxx> wrote:

Yes I am using milliseconds and yes it did take over 16 seconds - which is
why I need to confirm it didn't barf internally rather than actually
successfully complete the parsing process. It could be that 140kb managed
to blow its brains out.



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.