Sebastix's avatar
Sebastix _@sebastix.dev 1 week ago
I instructed the robot to optimize the current migration scripts (using a hybrid model with Python and Go) for creating keypairs, profile metadata + relay list events for @Nyves (there are 9.6 millions profiles to be migrated). There are now 100.000 profiles on the @Nyves relay. image This migration took 4.5 hours. That's not fast enough, so I will keep pushing the robot to do better (execute more async concurrent tasks). Otherwise I will just run the migration for 2-3 weeks ;-) Will push the current code in public soon in a ngit repo.

Replies (11)

Constant's avatar
Constant 1 week ago
you can borrow my fpga if you want :P
Constant's avatar
Constant 1 week ago
hahaha even with the help of AI it will probably take longer to program the thing than running the migration with the code you have right now.... Programming my FPGA using AI is one of the bazillion things on my to-do list 🤕
2 replies ↓
Constant's avatar
Constant 1 week ago
not to mention all the Software defined radio hardware i have laying around🫠
Sebastix's avatar
Sebastix _@sebastix.dev 1 week ago
I doubt that as long as I know what the bottlenecks are in the code where the robot needs to pay attention. I actually read the code what the robot delivers. I’m asking technical questions so the robot goes in a reflection mode. Learn the robot how to learn. 🤓
1 replies ↓
Sebastix's avatar
Sebastix _@sebastix.dev 6 days ago
And with this, you start pushing the robot to have a look at the concurrency stuff in the code and let it analyze how performant it is (not). image
Sebastix's avatar
Sebastix _@sebastix.dev 4 days ago
Yes I’m processing the data from the public data which has been archived by The Archive Team in 2013 Only usernames so far, which is already a ton of data
2 replies ↓
↑