BTW, it's wise to do `raco pollen setup` (which is parallel by default) before 
`raco pollen render -p`.


> On 06 27 19, at 7:32 PM, Shrutarshi Basu <s...@basus.me> wrote:
> 
> Hmm interesting, I reset the cache using `raco pollen reset` and then run 
> `raco pollen render -p` as well as `make -B -j 4` (the -B option forces 
> rebuild of all targets). Here's what I get:
> 
> raco pollen render -p  10.68s user 2.16s system 223% cpu 5.751 total
> 
> make -B -j 4  20.19s user 4.55s system 236% cpu 10.456 total
> 
> Looks like render -p is the way to go.
> 
> Thanks,
> Basu
> 
> On Thu, Jun 27, 2019 at 6:01 PM Matthew Butterick <m...@mbtype.com 
> <mailto:m...@mbtype.com>> wrote:
> I just use `raco pollen render -p` rather than plain `raco pollen render` in 
> my Makefile, for the top directory in the project.
> 
> I'd guess this is more efficient than `make -j x` because all the files are 
> inventoried and then doled out to each processor as fast as they can be 
> rendered. But try it and let me know if that's not so.
> 
> 
>> On Jun 27, 2019, at 1:23 PM, Shrutarshi Basu <s...@basus.me 
>> <mailto:s...@basus.me>> wrote:
>> 
>> This is great. I'm wondering how this should affect Makefile-driven setups? 
>> Currently I have a project with a bunch of directories, and a Makefile that 
>> runs `raco pollen render` for all the directories, and then publish at the 
>> toplevel directory. I've been running it `make -j 4` (since that's how many 
>> cores I have), but maybe there's a better way to do it? Should I just use 
>> `raco pollen render --recursive` at the toplevel and let pollen figure 
>> everything out?
> 
> 
> 
> -- 
> Shrutarshi Basu
> Basus.me <http://basus.me/>
> The ByteBaker <http://bytebaker.com/> -- computer science is not about 
> computers
> @basus <http://twitter.com/basus>
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Pollen" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to pollenpub+unsubscr...@googlegroups.com 
> <mailto:pollenpub+unsubscr...@googlegroups.com>.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/pollenpub/CA%2BYT8WiEp-vOusw7vHqszpqjY%3DVp7LnEgJmHLvcibRFnAQVUTg%40mail.gmail.com
>  
> <https://groups.google.com/d/msgid/pollenpub/CA%2BYT8WiEp-vOusw7vHqszpqjY%3DVp7LnEgJmHLvcibRFnAQVUTg%40mail.gmail.com?utm_medium=email&utm_source=footer>.
> For more options, visit https://groups.google.com/d/optout 
> <https://groups.google.com/d/optout>.

-- 
You received this message because you are subscribed to the Google Groups 
"Pollen" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to pollenpub+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/pollenpub/EC5D281C-45DB-4FD2-BE26-DE3FD90102B7%40mbtype.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to