Hacker News new | past | comments | ask | show | jobs | submit login

I've taken a very naive approach and it does NOT scale. It uses python multiprocessing. I think the fScore updates pickling and serialization - communication and synchronization lock overhead is slowing it down. It simply does not parallelise.

This is my code generator/program synthesiser, it synthesises assembly instructions from two given states of memory and registers to take it from one to the other, including hidden states such as functions.

https://replit.com/@Chronological/SlidingPuzzle3#main.py




Thanks, regardless of ability to parallelise it looks interesting.


I've changed the algorithm to not send fScore updates and treat each branch as independent.

This speeds it up from 16 seconds to 320 milliseconds. I am thinking how to make the algorithm scale, by creating better and alternative program candidates in each thread.




Join us for AI Startup School this June 16-17 in San Francisco!

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: