title: Concurrency, how to create an efficient actor setup?
body: <p>Alright so I have never done intense concurrent operations like this before, theres three main parts to this algorithm.</p>
  
  <p>This all starts with a Vector of around 1 Million items.
  Each item gets processed in 3 main stages.</p>
  
  <p>Task 1: Make an HTTP Request, Convert received data into a map of around 50 entries.
  Task 2: Receive the map and do some computations to generate a class instance based off the info found in the map.
  Task 3: Receive the class and generate/add to multiple output files.</p>
  
  <p>I initially started out by concurrently running task 1 with 64K entries across 64 threads (1024 entries per thread.). Generating threads in a for loop.</p>
  
  <p>This worked well and was relatively fast, but I keep hearing about actors and how they are heaps better than basic Java threads/Thread pools. I've created a few actors etc. But don't know where to go from here.</p>
  
  <p>Basically:
   1. Are actors the right way to achieve fast concurrency for this specific set of tasks. Or is there another way I should go about it.
   2. How do you know how many threads/actors are too many, specifically in task one, how do you know what the limit is on number of simultaneous connections is (Im on mac). Is there a golden rue to follow? How many threads vs how large per thread pool? And the actor equivalents?
   3. Is there any code I can look at that implements actors for a similar fashion? All the code Im seeing is either getting an actor to print hello world, or super complex stuff.</p>