Wrong confirmation ID
  • Email
  • Favorite
  • Download
  • Embed
  • Private Content

Loading…

Flash Player 9 (or above) is needed to view presentations.
We have detected that you do not have it on your computer. To install it, go here.

Introduction to node.js

by jacekbecela on Feb 24, 2010

  • 11,308 views

Slides I presented in srug.pl meeting on February 26, 2010

Slides I presented in srug.pl meeting on February 26, 2010

Accessibility

Categories

Tags

nodejs javascript event loop node-js nodejs javascript js

More...

Upload Details

Uploaded via SlideShare as Apple Keynote

Usage Rights

CC Attribution-ShareAlike LicenseCC Attribution-ShareAlike License

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate. If needed, use the feedback form to let us know more details.

Cancel

4 Embeds 59

http://www.slideshare.net 46
http://mj89sp3sau2k7lj1eg3k40hkeppguj6j-a-sites-opensocial.googleusercontent.com 7
http://www.tipiweb.tk 5
http://migueldev.com 1

Statistics

Favorites
17
Downloads
243
Comments
2
Embed Views
59
Views on SlideShare
11,249
Total Views
11,308

12 of 2 previous next

  • jacekbecela jacekbecela If this is a background process then you're fine - it probably doesn't matter too much. If you're inside a web server - try http://nodejs.org/docs/v0.3.7/api/child_processes.html (this approach also nicely scales across multiple cpu cores). 'Action rendering time' > 'The x seconds of continuous processing without letting go of the CPU'. Less than 100ms is good. Some people say: 'well, it depends' ;) 1 year ago Reply
    Are you sure you want to Yes No
  • voytek9 voytek9 You write on slide 49, 'Callbacks have to return fast -- no CPU heavy stuff.' I want to move from a blocking web spider that also does some keyword matching against the returned page, to using non-blocking node stuff. Can you please give me a vague scale of an acceptable range for returning fast? I envision using node to pull a page from a remote server, then perform the keyword processing on it (less than 1s of processing for sure). Is that too CPU heavy / too long of an execution time? 1 year ago Reply
    Are you sure you want to Yes No
Post Comment
Edit your comment Cancel

Introduction to node.js — Presentation Transcript