http://debianws.lexgopc.com/wiki143/index.php?action=history&feed=atom&title=AutoFetch 2026-10-26T21:11:52Z Revision history for this page on the wiki MediaWiki 1.43.1 http://debianws.lexgopc.com/wiki143/index.php?title=AutoFetch&diff=6688396&oldid=prev 2024-01-12T14:58:06Z

<p>Add citation to the relevant paper that first introduced autofetch, attempt to improve opening description.</p> <p><b>New page</b></p><div>{{Multiple issues|<br /> {{advert|date=January 2018}}<br /> {{Refimprove|date=October 2021}}<br /> }}<br /> &#039;&#039;&#039;AutoFetch&#039;&#039;&#039;&lt;ref&gt;{{cite web |last1=Ibrahim |first1=Ali |last2=Cook |first2=William |title=Automatic Prefetching by Traversal Profiling in Object Persistence Architectures |url=https://www.cs.utexas.edu/users/wcook/papers/AutoFetch/autofetch.pdf |access-date=12 January 2024}}&lt;/ref&gt; is a technique for automating the normally manual process of specifying prefetching hints for [[object–relational mapping]] queries.<br /> <br /> Ali Ibrahim and William Cook at the University of Texas at Austin developed the idea of &quot;AutoFetch&quot; including an implementation for [http://sourceforge.net/projects/autofetch Hibernate] and followed later by an implementation in [[Ebean]].<br /> <br /> == Benefits ==<br /> <br /> === Improving the modularity of application code ===<br /> AutoFetch uses the [[State (computer science)|program state]] (typically the [[call stack]]) to classify [[Information retrieval|queries]]. This means that AutoFetch can tune the same query in different ways depending on HOW it was called. <br /> <br /> For example, a Data Access API such as &lt;code&gt;findCustomer(int customerId)&lt;/code&gt; can be tuned differently depending on the callers of the method.<br /> <br /> === Reducing the development and maintenance burden from Developers ===<br /> Because AutoFetch automatically gathers the profiling information developers do not need to manually try and gather this information and apply performance optimizations to the code.<br /> <br /> AutoFetch can monitor the object graph usage so that if the usage changes, the tuning of the query can change to suit. This reduces the code maintenance issues for developers and maintains optimal performance as usage changes over time.<br /> <br /> == Working Principle ==<br /> AutoFetch collects object graph usage when queries are executed. It collects the &#039;profile&#039; information which is later used to automatically tune the query on subsequent executions. The ORM query is tuned by determining and automatically adding the correct prefetch directives for each query.<br /> <br /> This has shown to improve the performance of the application by reducing &quot;[[lazy loading]]&quot;. For ORMs that support partial objects, AutoFetch is able to also tune the query by including the properties that the application uses rather than all properties.<br /> <br /> == See also ==<br /> * [[Object–relational mapping]]<br /> * [[Hibernate (Java)|Hibernate]]<br /> * [[Ebean]]<br /> <br /> == References ==<br /> {{Reflist}}<br /> <br /> == External links ==<br /> * https://web.archive.org/web/20080418084615/http://www.cs.utexas.edu/~aibrahim/autofetch/<br /> * http://sourceforge.net/projects/autofetch/<br /> <br /> [[Category:Object–relational mapping]]</div>

imported>Toa697