• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
Multitasking in applications
 

Multitasking in applications

on

  • 1,290 views

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 ...

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.

Statistics

Views

Total Views
1,290
Views on SlideShare
1,125
Embed Views
165

Actions

Likes
0
Downloads
5
Comments
0

5 Embeds 165

http://www.sadev.co.za 153
http://sadev.co.za 5
http://feeds.feedburner.com 4
http://maclean.nom.za 2
http://173.245.56.11 1

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

CC Attribution-ShareAlike LicenseCC Attribution-ShareAlike License

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    Multitasking in applications Multitasking in applications Presentation Transcript

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