True, I can live with the speed that it is currently running. I was willing
to construct 4 workers in hopes of getting it down to 15 minutes. To be
able to have it running in my main application in under three minutes is a
dream. Now it is just a fun academic exercise for me. So, I am definitely
going to try the Pythagorean theorem and see if it is close enough and
faster. But I am also interested in trying to create a table to look up
previous calculated values to see if I can make it any faster. I don't know
if Flex is going to allow this. A 38k x 38k table has 1,444,000,000 values
that it can hold, and that is a lot of Gigabytes for Flex. I tried to
create a vector this big and Flex gave up and just closed. This is how I
tried to create it:
var vector:Vector.<Vector.<Number>> = new
Vector.<Vector.<Number>>(length);
for (var k:int = 0; k < length; k++) {
vector[k] = new Vector.<Number>(length);
}
Flex didn't like this. The thing is, I don't need for a cell to be created
to hold something if there is nothing to put it in. So if I calculate
distances and only place them in an array if they are appropriate
comparisons, I may only have an array with a few million cells populated. I
don't know if Flex will only increase memory on an array if it is needed. Do
you think an Array is a better choice than a Vector here?
--
View this message in context:
http://apache-flex-users.2333346.n4.nabble.com/Workers-and-Speed-tp13098p13206.html
Sent from the Apache Flex Users mailing list archive at Nabble.com.
