PageRenderTime 26ms CodeModel.GetById 10ms RepoModel.GetById 0ms app.codeStats 0ms

/docs/homepage/celery_1.0_released.html

https://github.com/coderanger/celery
HTML | 236 lines | 219 code | 17 blank | 0 comment | 0 complexity | acb3e8e37689c67a2bbe837f9ee55cc9 MD5 | raw file
    

  1. <!DOCTYPE html>
    2. 

  2. <html>
    3. 

  3. <head>
    4. 

  4. <meta charset="utf-8">
    5. 

  5. <meta name="keywords" content="task queue, job queue, asynchronous, rabbitmq, amqp,
    6. 

  6. redis, django, python, webhooks, queue, distributed">
    7. 

  7. <meta name="description" content="open source distributed task queue" >
    8. 

  8. <link rel="icon" type="image/png" href="favicon.png">
    9. 

  9. <meta name="viewport" content="width=320, user-scalable=no">
    10. 

  10. <link rel="apple-touch-icon" href="favicon_64.png"/>
    11. 

  11. <title>Celery - The Distributed Task Queue</title>
    12. 

  12. <link rel="stylesheet" href="main.css"/>
    13. 

  13. <link rel="stylesheet" href="trac.css"/>
    14. 

  14. <script type="text/javascript">
    15. 

  15. var gaJsHost = (("https:" == document.location.protocol) ? "https://ssl." : "http://www.");
    16. 

  16. document.write(unescape("%3Cscript src='" + gaJsHost + "google-analytics.com/ga.js' type='text/javascript'%3E%3C/script%3E"));
    17. 

  17. </script>
    18. 

  18. <script type="text/javascript">
    19. 

  19. try {
    20. 

  20. var pageTracker = _gat._getTracker("UA-12986238-1");
    21. 

  21. pageTracker._trackPageview();
    22. 

  22. } catch(err) {}</script>
    23. 

  23. 

  24. </head>
    25. 

  25. 

  26. <body>
    27. 

  27. <div id="navbar">
    28. 

  28.   <div class="iStretch">
    29. 

  29.     <div class="link" id="current"><a href="/">Home</a></div>
    30. 

  30.     <div class="link"><a href="http://github.com/ask/celery">Code</a></div>
    31. 

  31.     <div class="link"><a href="docs/">Documentation</a></div>
    32. 

  32.     <div class="link"><a href="http://ask.github.com/celery/getting-started/">Tutorials</a></div>
    33. 

  33.     <div class="link"><a href="http://pypi.python.org/pypi/celery">Download</a></div>
    34. 

  34.   </div>
    35. 

  35. </div>
    36. 

  36. 

  37. <div class="iStretch">
    38. 

  38. 

  39.   <div id="topcontainer">
    40. 

  40.   <ul>
    41. 

  41.     <li>Background Processing
    42. 

  42.     <li>Distributed
    43. 

  43.     <li>Asynchronous/Synchronous
    44. 

  44.     <li>Concurrency
    45. 

  45.     <li>Periodic Tasks
    46. 

  46.     <li>Retries
    47. 

  47.   </ul>
    48. 

  48.   </div>
    49. 

  49. 

  50.   <div id="contentcontainer">
    51. 

  51. 

  52.     <div class="column">
    53. 

  53. <h1>Celery 1.0 has been released!</a></h1>
    54. 

  54. <p>We&#8217;re happy to announce the release of Celery 1.0.</p>
    55. 

  55. <div class="section" id="what-is-it">
    56. 

  56. <h2>What is it?</h2>
    57. 

  57. <p>Celery is a task queue/job queue based on distributed message passing.
    58. 

  58. It is focused on real-time operation, but supports scheduling as well.</p>
    59. 

  59. <p>The execution units, called tasks, are executed concurrently on one or
    60. 

  60. more worker servers. Tasks can execute asynchronously (in the background) or synchronously
    61. 

  61. (wait until ready).</p>
    62. 

  62. <p>Celery is already used in production to process millions of tasks a day.</p>
    63. 

  63. <p>Celery was originally created for use with Django, but is now usable
    64. 

  64. from any Python project. It can
    65. 

  65. also operate with other languages via webhooks.</p>
    66. 

  66. <p>The recommended message broker is <a class="reference external" href="http://rabbitmq.org">RabbitMQ</a>, but support for Redis or
    67. 

  67. database is also available.</p>
    68. 

  68. <div class="section" id="features">
    69. 

  69. <h3>Features</h3>
    70. 

  70. <p>See <a class="reference external" href="http://ask.github.com/celery/getting-started/introduction.html#features">http://ask.github.com/celery/getting-started/introduction.html#features</a></p>
    71. 

  71. </div>
    72. 

  72. </div>
    73. 

  73. <div class="section" id="stable-api">
    74. 

  74. <h2>Stable API</a></h2>
    75. 

  75. <p>From this version on the public API is considered stable. This means there won&#8217;t
    76. 

  76. be any backwards incompatible changes in new minor versions. Changes to the
    77. 

  77. API will be deprecated; so, for example, if we decided to remove a function
    78. 

  78. that existed in Celery 1.0:</p>
    79. 

  79. <ul class="simple">
    80. 

  80. <li>Celery 1.2 will contain a backwards-compatible replica of the function which
    81. 

  81. will raise a <tt class="docutils literal"><span class="pre">PendingDeprecationWarning</span></tt>.
    82. 

  82. This warning is silent by default; you need to explicitly turn on display
    83. 

  83. of these warnings.</li>
    84. 

  84. <li>Celery 1.4 will contain the backwards-compatible replica, but the warning
    85. 

  85. will be promoted to a full-fledged <tt class="docutils literal"><span class="pre">DeprecationWarning</span></tt>. This warning
    86. 

  86. is loud by default, and will likely be quite annoying.</li>
    87. 

  87. <li>Celery 1.6 will remove the feature outright.</li>
    88. 

  88. </ul>
    89. 

  89. <p>See the <a class="reference external" href="http://ask.github.com/celery/internals/deprecation.html">Celery Deprecation Timeline</a> for a list of pending removals.</p>
    90. 

  90. </div>
    91. 

  91. <div class="section" id="what-s-new">
    92. 

  92. <h2>What&#8217;s new?</h2>
    93. 

  93. <ul>
    94. 

  94. <li><p class="first">Task decorators</p>
    95. 

  95. <p>Write tasks as regular functions and decorate them.
    96. 

  96. There are both <tt class="xref docutils literal"><span class="pre">task()</span></tt>, and <tt class="xref docutils literal"><span class="pre">periodic_task()</span></tt> decorators.</p>
    97. 

  97. </li>
    98. 

  98. <li><p class="first">Tasks are automatically registered</p>
    99. 

  99. <p>Registering the tasks manually was getting tedious, so now you don&#8217;t have
    100. 

  100. to anymore. You can still do it manually if you need to, just
    101. 

  101. disable <tt class="xref docutils literal"><span class="pre">Task.autoregister</span></tt>. The concept of abstract task classes
    102. 

  102. has also been introduced, this is like django models, where only the
    103. 

  103. subclasses of an abstract task is registered.</p>
    104. 

  104. </li>
    105. 

  105. <li><p class="first">Events</p>
    106. 

  106. <p>If enabled, the worker will send events, telling you what tasks it
    107. 

  107. executes, their results, and how long it took to execute them. It also
    108. 

  108. sends out heartbeats, so listeners are able to detect nonfunctional
    109. 

  109. workers. This is the basis for the new real-time web monitor we&#8217;re working on
    110. 

  110. (<a class="reference external" href="http://github.com/ask/celerymon/">celerymon</a>)</p>
    111. 

  111. </li>
    112. 

  112. </ul>
    113. 

  113. <ul>
    114. 

  114. <li><p class="first">Rate limiting</p>
    115. 

  115. <p>Global and per task rate limits. 10 tasks a second? or one an hour? You
    116. 

  116. decide. It&#8217;s using the awesome <a class="reference external" href="http://en.wikipedia.org/wiki/Token_bucket">token bucket algorithm</a>, which is
    117. 

  117. commonly used for network traffic shaping. It accounts for bursts of
    118. 

  118. activity, so your workers won&#8217;t be bored by having nothing to do.</p>
    119. 

  119. </li>
    120. 

  120. </ul>
    121. 

  121. <ul>
    122. 

  122. <li><p class="first">New periodic task service.</p>
    123. 

  123. <p>Periodic tasks are no longer dispatched by <tt class="docutils literal"><span class="pre">celeryd</span></tt>, but instead by a
    124. 

  124. separate service called <tt class="docutils literal"><span class="pre">celerybeat</span></tt>. This is an optimized, centralized
    125. 

  125. service dedicated to your periodic tasks, which means you don&#8217;t have to
    126. 

  126. worry about deadlocks or race conditions any more. But that does mean you
    127. 

  127. have to make sure only one instance of this service is running at any one
    128. 

  128. time.</p>
    129. 

  129. <p><strong>TIP:</strong> If you&#8217;re only running a single <tt class="docutils literal"><span class="pre">celeryd</span></tt> server, you can embed
    130. 

  130. <tt class="docutils literal"><span class="pre">celerybeat</span></tt> inside it. Just add the <tt class="docutils literal"><span class="pre">--beat</span></tt> argument.</p>
    131. 

  131. </li>
    132. 

  132. <li><p class="first">Broadcast commands</p>
    133. 

  133. <p>If you change your mind and don&#8217;t want to run a task after all, you
    134. 

  134. now have the option to revoke it.</p>
    135. 

  135. <p>Also, you can rate limit tasks or even shut down the worker remotely.</p>
    136. 

  136. <p>It doesn&#8217;t have many commands yet, but we&#8217;re waiting for broadcast
    137. 

  137. commands to reach its full potential, so please share your ideas
    138. 

  138. if you have any.</p>
    139. 

  139. </li>
    140. 

  140. <li><p class="first">Multiple queues</p>
    141. 

  141. <p>The worker is able to receive tasks on multiple queues at once.
    142. 

  142. This opens up a lot of new possibilities when combined with the impressive
    143. 

  143. routing support in AMQP.</p>
    144. 

  144. </li>
    145. 

  145. <li><p class="first">Platform agnostic message format.</p>
    146. 

  146. <p>The message format has been standardized and is now using the ISO-8601 format
    147. 

  147. for dates instead of Python <tt class="docutils literal"><span class="pre">datetime</span></tt> objects. This means you can write task
    148. 

  148. consumers in other languages than Python (<tt class="docutils literal"><span class="pre">eceleryd</span></tt> anyone?)</p>
    149. 

  149. </li>
    150. 

  150. <li><p class="first">Timely</p>
    151. 

  151. <p>Periodic tasks are now scheduled on the clock, i.e. <tt class="docutils literal"><span class="pre">timedelta(hours=1)</span></tt>
    152. 

  152. means every hour at :00 minutes, not every hour from the server starts.
    153. 

  153. To revert to the previous behavior you have the option to enable
    154. 

  154. <tt class="xref docutils literal"><span class="pre">PeriodicTask.relative</span></tt>.</p>
    155. 

  155. </li>
    156. 

  156. <li><p class="first">... and a lot more!</p>
    157. 

  157. </li>
    158. 

  158. </ul>
    159. 

  159. <p>To read about these and other changes in detail, please refer to
    160. 

  160. the <a class="reference external" href="http://ask.github.com/celery/changelog.html">changelog</a>. This document contains crucial information for those
    161. 

  161. upgrading from a previous version of Celery, so be sure to read the entire
    162. 

  162. change set before you continue.</p>
    163. 

  163. <p><strong>TIP:</strong> If you install the <tt class="xref docutils literal"><span class="pre">setproctitle</span></tt> module you can see which
    164. 

  164. task each worker process is currently executing in <tt class="docutils literal"><span class="pre">ps</span></tt> listings.
    165. 

  165. Just install it using pip: <tt class="docutils literal"><span class="pre">pip</span> <span class="pre">install</span> <span class="pre">setproctitle</span></tt>.</p>
    166. 

  166. </div>
    167. 

  167. <div class="section" id="resources">
    168. 

  168. <h2>Resources</h2>
    169. 

  169. <ul class="simple">
    170. 

  170. <li><a class="reference external" href="http://celeryproject.org/docs/">Documentation</a></li>
    171. 

  171. <li><a class="reference external" href="http://celeryproject.org/docs/changelog.html">Changelog</a></li>
    172. 

  172. <li><a class="reference external" href="http://ask.github.com/celery/faq.html">FAQ</a></li>
    173. 

  173. <li><a class="reference external" href="http://groups.google.com/group/celery-users">Mailing-list</a></li>
    174. 

  174. <li><a class="reference external" href="http://twitter.com/asksol">Twitter</a></li>
    175. 

  175. <li>IRC: #celery on irc.freenode.net.</li>
    176. 

  176. </ul>
    177. 

  177. </div>
    178. 

  178. 

  179. 

  180.     <div class="hidden">
    181. 

  181.         <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
    182. 

  182.         &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
    183. 

  183.         </p>
    184. 

  184.         <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
    185. 

  185.         &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
    186. 

  186.         </p>
    187. 

  187.         <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
    188. 

  188.         &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
    189. 

  189.         </p>
    190. 

  190.     </div>
    191. 

  191.     </div>
    192. 

  192. 

  193.     <div class="column">
    194. 

  194. 

  195.       <span class="newsitem">
    196. 

  196.       <h2>Celery 1.0 released!</h2>
    197. 

  197.       <h4>By <a href="http://twitter.com/asksol">@asksol</a> on 10.02.2010</h4>
    198. 

  198.       <p>Celery 1.0 has finally been released! It is available on <a
    199. 

  199.           href="http://pypi.python.org/pypi/celery/1.0.0">PyPI</a> for
    200. 

  200.       downloading. You can also install it via <code>pip install
    201. 

  201.           celery</code>. You can read the announcement <a href="celery_1.0_released.html">here</a>.
    202. 

  202.       <hr>
    203. 

  203.       </span>
    204. 

  204. 

  205.       <span class="newsitem">
    206. 

  206.       <h2>1.0 is in beta.</h2>
    207. 

  207.       <h4>By <a href="http://twitter.com/asksol">@asksol</a> on 08.02.2010</h4>
    208. 

  208.       <p>1.0 is scheduled to be released this week! Please help us test the latest
    209. 

  209.       <a href="http://github.com/ask/celery/tarball/v1.0.0-pre4">release
    210. 

  210.           candiate</a> to make this happen. To upgrade from an earlier
    211. 

  211.       version, please read the <a href="http://ask.github.com/celery/changelog.html">changelog</a>.
    212. 

  212.       <hr>
    213. 

  213.       </span>
    214. 

  214. 

  215.       <span class="newsitem">
    216. 

  216.       <h2>New website.</h2>
    217. 

  217.       <h4>By <a href="http://twitter.com/asksol">@asksol</a> on 08.02.2010</h4>
    218. 

  218.       <p>We finally got a home page. Big thanks to <a href="http://helmersworks.com">Jan Henrik Helmers</a>
    219. 

  219.       <hr>
    220. 

  220.       </span>
    221. 

  221. 

  222.     </div>
    223. 

  223. 

  224.   </div>
    225. 

  225. 

  226.  <div id="credits">
    227. 

  227.      <div class="iStretch">Copyright (c) 2009-2010, <a href="http://twitter.com/asksol">Ask Solem</a> and
    228. 

  228.          <a href="http://github.com/ask/celery/blob/master/AUTHORS">contributors</a>.<br>
    229. 

  229.  Page design by <a href="http://www.helmersworks.com/">Jan Henrik Helmers</a>
    230. 

  230.    </div>
    231. 

  231.  </div>
    232. 

  232. 

  233. 

  234. </div>
    235. 

  235. </body>
    236. 

  236. </html>
    237. 

  237.