StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POJsoup: Performance of top-level select() vs. inner-level select()
primarykey
Id
7829555
data
AcceptedAnswerId
7831446
AnswerCount
1
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2011-10-19T23:43:12.793
FavoriteCount
0
LastActivityDate
2011-10-20T13:48:11.090
LastEditDate
2011-10-20T13:48:11.090
LastEditorUserId
576267
OwnerUserId
576267
ParentId
0
PostTypeId
1
Score
1
ViewCount
1071
LastEditorDisplayName
text
Body
My understanding is that once a document is loaded into Jsoup, using <code>Jsoup.parse()</code>, no parsing is required again as a neatly hierarchical tree is ready for programmer's use. But what I am not sure whether top-level select() is more costly than inner-level select(). For example, if we have a <code></code> buried inside many nested <code><div></code>s, and that <code></code>'s parent is already available in the program, will there be any performance difference between: <pre><code>document.select("p.pclass") </code></pre> and <pre><code>pImediateParent.select("p.pclass") </code></pre> ? How does that work in Jsoup? UPDATE: Based on the answer below, I understand that both <code>document.select()</code> and <code>pImediateParent.select()</code> use the <a href="http://massapi.com/source/jsoup-1.6.1-sources/org/jsoup/nodes/Element.java.html" rel="nofollow">same exact static method</a>, just with a different root as the second parameter: <pre><code>public Elements select(String query) { return Selector.select(query, this); } </code></pre> Which <a href="http://massapi.com/source/jsoup-1.6.1-sources/org/jsoup/select/Selector.java.html" rel="nofollow">translates into</a>: <pre><code>/** * Find elements matching selector. * * @param query CSS selector * @param root root element to descend into * @return matching elements, empty if not */ public static Elements select(String query, Element root) { return new Selector(query, root).select(); } </code></pre> I am not surprised, but the question now is how does that <code>query</code> work? Does it iterate to find the queried element? Is it a random access (as in hash table) query?
Tags
<java><html-parsing><jsoup>
Title
Jsoup: Performance of top-level select() vs. inner-level select()
singulars
PostAcceptedAnswerId
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. USRegex Rookie
UserOwnerUserId
1. USRegex Rookie
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 POJsoup: Performance of top-level select() vs. inner-level select()
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. This table or related slice is empty.

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.