You should definitely try worker, it may not get it down to 1/4 but it will be close most likely if the task is partitioned well.
On Sat, Jul 30, 2016, 9:11 PM bilbosax <waspenc...@comcast.net> wrote: > So my application is a HUGE number cruncher. But since it is running on > one > thread, the deployed version still takes about an hour to process my data. > If at all possible, I would like to get this down to about 15 minutes so I > could run it several times a day. My computer has two XEON Quad Cores and > almost 24GB of RAM, so I am not worried about overworking my machine. > Currently, my main application is running at about 150MB. > > So I am interested in speeding up my application using Workers. I have > never > tried using Workers to increase speed, so I wanted to ask people with > experience with Workers if you think it is worth the effort. By splitting > the processing load to four threads, do you think I could whittle the > processing time down to 15 minutes, or is there a point at which adding > more > threads just increases overhead, and therefore you don't gain much? Or is > it > hugely advantageous? > > > > -- > View this message in context: > http://apache-flex-users.2333346.n4.nabble.com/Workers-and-Speed-tp13098.html > Sent from the Apache Flex Users mailing list archive at Nabble.com. >
