Thanks Karl for the excellent links on Alchemy optimizations! Man this stuff is 
fiddly. If Adobe could just make their AS VM run as fast as the C# one, devs 
wouldn't need to jump through these hoops!

BTW, does anyone know whether is Alchemy still "pre-release"?  The Alchemy page 
at Adobe Labs...
  http://labs.adobe.com/technologies/alchem
...has this warning/disclaimer:

"The Alchemy preview is prerelease software that is not supported by Adobe and 
may contain bugs. It is therefore advised that Alchemy not be used to generate 
code for use in production." 

I vaguely remember seeing that disclaimer a year (or two?) ago. I wonder 
whether it's worth putting effort into learning the ins and outs of a 
technology that's not officially supported and into which Adobe appears to be 
putting few resources.

-Gerry

On 2011-07-20  , at 12:17 , Karl DeSaulniers wrote:

> Hi Gerry,
> Alchemy optimizations. They look like good reads.
> Hope they are along the lines of what your looking for.
> 
> http://blog.frankula.com/?p=211
> 
> http://philippe.elsass.me/2010/05/as3-fast-memory-access-without-alchemy/
> 
> 
> Best,
> Karl
> 
> On Jul 19, 2011, at 10:42 PM, Gerry Beauregard wrote:
> 
>> Hi Kevin,
>> 
>> Thanks for this!  Definitely interesting. In my limited testing with 
>> Alchemy, I found that getting large amounts of data across the AS3-Alchemy 
>> boundary using ByteArrays was indeed a major bottleneck, so anything that 
>> eliminates that bottleneck is welcome indeed!
>> 
>> -Gerry
>> 
>> On 2011-07-20  , at 07:09 , Kevin Newman wrote:
>> 
>>> Or Pixel Bender - I've heard you can do some heavy processing with that too.
>>> 
>>> Additionally, HaXe has some ways to avoid some of the overhead of Alchemy 
>>> when using it from AS3. You'd have to do a lot in haxe instead of AS3, but 
>>> you can use the alchemy stuff though inlining, which accesses the memory 
>>> stored in Alchemy directly, instead of copying data back and forth between 
>>> AS3 and Alchemy memory space, which if I understand it correctly, is where 
>>> the overhead is with Alchemy.
>>> 
>>> Joa has a tool (http://code.google.com/p/apparat/) which might be useful to 
>>> help do some AS3 inlining to the Alchemy memory operations. I think the way 
>>> to use it, is to make sure your bytearrays are stored in the Alchemy 
>>> memory. Then you can access that from AS3 without the memcopy overhead.
>>> 
>>> Kevin N.
>>> 
>>> 
>>> On 7/19/11 7:35 AM, Gerry Beauregard wrote:
>>>> On 2011-07-19  , at 18:07 , Leandro Ferreira wrote:
>>>> 
>>>>> Have you tried Alchemy?
>>>>> http://labs.adobe.com/technologies/alchemy/
>>>>> 
>>>>> *
>>>>> *
>>>>> *   @leandroferreira*
>>>>> *   55 61 91151257*
>>>> 
>>> 
>>> _______________________________________________
>>> Flashcoders mailing list
>>> Flashcoders@chattyfig.figleaf.com
>>> http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
>> 
>> 
>> _______________________________________________
>> Flashcoders mailing list
>> Flashcoders@chattyfig.figleaf.com
>> http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
> 
> Karl DeSaulniers
> Design Drumm
> http://designdrumm.com
> 
> _______________________________________________
> Flashcoders mailing list
> Flashcoders@chattyfig.figleaf.com
> http://chattyfig.figleaf.com/mailman/listinfo/flashcoders


_______________________________________________
Flashcoders mailing list
Flashcoders@chattyfig.figleaf.com
http://chattyfig.figleaf.com/mailman/listinfo/flashcoders

Reply via email to