Sun May 25 05:33:19 PDT 2008
threadsafe as the backend it targets. In other words your mileage may vary.
Win32 GDI for example can not share a DeviceContext between threads.
On Sun, May 25, 2008 at 8:29 AM, KwangYul Seo <kwangyul.seo at gmail.com>
> I asked the same question here, but got no response. I tested drawing to
> the same surface by multiple threads. I used ImageSurface and the result was
> promising. I could reduce the total drawing time by factor of almost 2 in my
> dual core processor.
> When you have multiple threads with their own cairo context, you can do
> high-level graphics operations such as tessellation in parallel, so you can
> get performance boost regardless of the underlying surface. However, I am
> not sure this approach is thread-safe across various cairo back-ends.
> What is the plan to optimize cairo with the advent of multi-core
> processors? Creating multiple cairo contexts with multiple threads to the
> same surface is the right approach?
> Kwang Yul Seo
> On Tue, May 20, 2008 at 8:40 AM, Augusto Radtke <radtke at radtke.com.br>
>> Hello! I couldn't found this answer in the usual places, so maybe someone
>> here can. It's possible to draw to the same surface by multiple threads? I
>> mean creating two contexts, one with each thread and clip it to different
>> regions of the surface and draw in parallel?
>> The idea is to reduce the total drawing time but I feel this feature could
>> be backend-specific and for some backend won't be really useful at all. Am I
>> Thank you,
>> cairo mailing list
>> cairo at cairographics.org
> cairo mailing list
> cairo at cairographics.org
Content-Type: text/html; charset=ISO-8859-1
More information about the cairo