On Sun, Aug 16, 2020 at 8:43 PM Linas Vepstas <[email protected]> wrote:
> > > On Sun, Aug 16, 2020 at 5:24 PM Predrag Radović <[email protected]> > wrote: > >> Hi Linas, >> > > >> All in all, I expect much better performance with very concurrent >> workloads, >> hundreds of threads. When a processing thread hits a page which is not >> yet in >> physical RAM it blocks. Request for that page from storage is queued. >> Other >> threads continue to work and after some time they will block too waiting >> for >> some of their pages to load. Storage layer will collect multiple >> requests and >> deliver data in batches, introducing latency. That's why when they >> benchmark >> SSDs there are graphs for various queue depths. Deeper queue, better >> throughput. >> > > OK, so these tests are "easily" parallelized, with appropriate definition > of "easy". Each search is conducted on each gene separately, so these can > be run in parallel. That's the good news. > The other good news is that Atomese has several actual Atoms that run > multiple threads -- one called ParallelLink, the other called > JoinThreadLink. I've never-ever tried them with the pattern matcher before. > I will try now ... > I tried. It works-ish. (actually, it works-ish great, with the appropriate definition of "great"; I'm thrilled.) The JoinThreadLink does parallelize, but it has a rather old API that predates modern ideas that makes it currently impractical. I need to fix it .. which should be "easy" cause no one currently uses it. But this will take at least a few days or longer, and I really should be doing other things... like plumbing in the upstairs bathroom... I (really?) like this idea, since, done right, it might be the easiest way to parallelize queries, which has been a sticking point for a while. We've got all the other parallel infrastructure in place, already, so now it just has to be wired up correctly. -- Linas -- Verbogeny is one of the pleasurettes of a creatific thinkerizer. --Peter da Silva -- You received this message because you are subscribed to the Google Groups "opencog" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/opencog/CAHrUA35mRfkCYZ%2Bb9WUpn%2BT1iKDP8fmQG0vz_wbdP0rHfG3CpA%40mail.gmail.com.
