• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Thread count strangeness using PlayAudioFile sample code
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Thread count strangeness using PlayAudioFile sample code


  • Subject: Re: Thread count strangeness using PlayAudioFile sample code
  • From: Shawn Erickson <email@hidden>
  • Date: Tue, 29 Mar 2005 14:27:06 -0800


On Mar 29, 2005, at 1:23 PM, Chris Weare wrote:

If there is a concern about creation cost then why is a new thred being created each time. I would think that if the concern is to not pay the creation cost when you are ready to go then a good pattern to use is a thred pool where the threads are created up front during init time then round-robin through the work.

I had read his message to say that exactly one thread was created in total not that multiple threads got created as he ran (one each time he called PLayAudioFile).


Paying for each creation AT call time in the hopes that one MIGHT save later seems odd.

Which was not what I was trying to say was going on.

-Shawn

_______________________________________________
Do not post admin requests to the list. They will be ignored.
Coreaudio-api mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


References: 
 >Re: Thread count strangeness using PlayAudioFile sample code (From: "Chris Weare" <email@hidden>)

  • Prev by Date: Re: Thread count strangeness using PlayAudioFile sample code
  • Next by Date: Elementary CoreMIDI problem
  • Previous by thread: Re: Thread count strangeness using PlayAudioFile sample code
  • Next by thread: Elementary CoreMIDI problem
  • Index(es):
    • Date
    • Thread