Databases
StackOverflow2013
Postsdbo
POHow Can I Speed Up Android XML Parsing?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POHow Can I Speed Up Android XML Parsing?
    primarykey
    data
    text
    <p>Good afternoon (depending on where you live)!</p> <p>I'm fairly new to Android development and I'm currently working on moving the functionality from an existing iOS app to Android. Part of this functionality is to parse a "large" (~13,000 line) RSS XML file that contains about 500 entries. I've spent anywhere from 10-15 hours researching XML parsing on Android AND trying out the major XML parsers: DOM, SAX, and Pull-parsing. Here are my results, running within' the emulator on my box (32-bit Windows Vista, 2.2 GHz Dual CPU, 3 GB RAM):</p> <p>SAX: ~6:00 minutes</p> <p>Pull-Parsing: ~4:00 minutes</p> <p>DOM: Greater than 4:00 minutes, but didn't time it when I had that implementation coded.</p> <p>I also tried this RSS Reader from github, but it took >10:00 minutes:</p> <p><a href="https://github.com/matshofman/Android-RSS-Reader-Library" rel="noreferrer">https://github.com/matshofman/Android-RSS-Reader-Library</a></p> <p>The implementations for the SAX, PP, and DOM were all taken from stackoverflow.com threads, so I feel fairly confident that I didn't do anything non-standard in them (though, I'm not ruling that out). I've decided to appeal to a larger, more experienced, crowd to get some ideas of what else I can try.</p> <p>I don't have any control over the format of the file. If I was implementing this end-to-end, I would just write a Web Service that did all the heavy-lifting on the server and then sent down a small, compact, JSON-serialized list. Instead, I have the 13K line file. :)</p> <p>Any insight into what I can do? It seems to be a fairly common problem, but most responses just say to try one of the different main XML parsers. In my case, I've tried all three and even the fastest seems way too slow.</p> <p>What am I doing wrong? Are there any normal "newbie" problems that people usually encounter when doing XML parsing over the network on Android???</p> <p>Thank you in advance for any help you can provide!</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USMr. Spock
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POHow Can I Speed Up Android XML Parsing?
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POHow Can I Speed Up Android XML Parsing?
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POHow Can I Speed Up Android XML Parsing?
      1. This table or related slice is empty.
      1. VTUpMod
    1. COIs it static content? You could convert it to JSON (there are converters online and a number of text editors that will do the job). For regular data, JSON is much faster.
      singulars
      1. POHow Can I Speed Up Android XML Parsing?
      1. USSimon
    2. COUnfortunately no, it is NOT static - it's changed a couple times a week as more messages are recorded. What you suggest IS interesting, though. Since it changes so infrequently I COULD convert it periodically, but that just adds something else to the mix I have to deal with. Good info and I'll take what you have recommended into consideration.
      singulars
      1. POHow Can I Speed Up Android XML Parsing?
      1. USMr. Spock
    3. COto the end to end (wish it was json) bit. What if you wrote a piggyback server app. I've done this for my apps when the source content was nuts. My app hits a service that hits the actual destination. Loaded it up on heroku (free) and it was all good.
      singulars
      1. POHow Can I Speed Up Android XML Parsing?
      1. USbaash05
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload