Diese Präsentation wurde erfolgreich gemeldet.
Wir verwenden Ihre LinkedIn Profilangaben und Informationen zu Ihren Aktivitäten, um Anzeigen zu personalisieren und Ihnen relevantere Inhalte anzuzeigen. Sie können Ihre Anzeigeneinstellungen jederzeit ändern.
Multitasking in Applications<br />
why?<br />no arguments against needing to be multi-something?<br />avg cores on desktop: 2.68<br />cloud: scalable because...
Some are more equal than others<br />Common logic of add threads = going faster is just wrong.<br />Physical CPU core limi...
Threading is just hard<br />Code complexity<br />Providing results at the end of processing<br />Cross thread communicatio...
what does .NET give us?<br />
The trend?<br />Threading is done<br />Done != Dead<br />Not much more can be added or changed<br />Easier with thread poo...
demo time<br />
Other options?<br />Reactive Extensions<br />Qbservable<br />All those good ideas from the 60’s like pub/sub<br />
Summary<br />Their goal is to make this easier<br />Stop thinking in threads<br />On going process of evaluate, test & rev...
Nächste SlideShare
Wird geladen in …5
×

Multitasking in applications

1.526 Aufrufe

Veröffentlicht am

If you are still thinking in threads when you want code to run in parallel you are doing it wrong. Multitasking is the new hotness and .NET Framework 4 provides many features for the creation of tasks, which is an abstraction above threads, to make your life WAY easier.

Veröffentlicht in: Technologie, Business
  • Als Erste(r) kommentieren

  • Gehören Sie zu den Ersten, denen das gefällt!

Multitasking in applications

  1. 1. Multitasking in Applications<br />
  2. 2. why?<br />no arguments against needing to be multi-something?<br />avg cores on desktop: 2.68<br />cloud: scalable because of lots of small parts working separately <br />
  3. 3. Some are more equal than others<br />Common logic of add threads = going faster is just wrong.<br />Physical CPU core limits<br />Balancing cost to create vs. benefit<br />I/O bound vs. CPU bound<br />
  4. 4. Threading is just hard<br />Code complexity<br />Providing results at the end of processing<br />Cross thread communication<br />Updating the UI<br />Logic issues<br />Balancing new threads vs. reusing threads<br />Really understanding the bottlenecks<br />
  5. 5. what does .NET give us?<br />
  6. 6. The trend?<br />Threading is done<br />Done != Dead<br />Not much more can be added or changed<br />Easier with thread pools<br />Tasking is the new trend<br />Threading lite<br />Easier to consume<br />
  7. 7. demo time<br />
  8. 8. Other options?<br />Reactive Extensions<br />Qbservable<br />All those good ideas from the 60’s like pub/sub<br />
  9. 9. Summary<br />Their goal is to make this easier<br />Stop thinking in threads<br />On going process of evaluate, test & review<br />

×