06:36 <rori[m]> will also be quiet on monday (internal events) but will be here on tuesday so will make it to the GSoC meeting

12:55 <srinivasyadav227> any reasons why `hpx::compute::vector` is slower than `std::vector`?

13:11 <srinivasyadav227> when performing benchmarks I see a greater speed up for `hpx vector seq over par` than `std vector seq over par`, but `hpx vector seq and par` take more time to run than `std vector seq and par`

14:29 <dkaratza[m]> i updated the pr but [skip ci] was removed from the description and i dont know why...

14:30 <hkaiser> dkaratza[m]: I think ms[m] changed the Jenkins configuration such that it looks at the ticket label 'category: documentation' instead

14:31 <dkaratza[m]> hkaiser: so there is no need for adding [skip ci] anymore?

14:31 <hkaiser> nod, presumably

14:32 <hkaiser> we are not sure yet whether this actually works as expected, yet

16:41 <jedi18[m]> hkaiser: I'm still getting the same error in the starts_with test, though very rarely

16:55 <hkaiser> jedi18[m]: ok

18:22 <dkaratza[m]> Since we said that we would like to merge the tables at https://hpx-docs.stellar-group.org/branches/master/html/manual/building_hpx.html#software-and-libraries, I assume that the new table containing all the other should be called "Software prerequisites for HPX"? I'm asking because some of these prerequisites now are mentioned as optional. By merging the tables we make them mandatory, right?

18:23 <dkaratza[m]> I'm talking about google-perftools, papi, mi-malloc and jemalloc actually, since the rest of the optional prerequisites will be removed

18:28 <hkaiser> dkaratza[m]: we should merge the linux/windows tables

18:28 <hkaiser> we can keep the mandatory and optional prerequisites in separate tables

18:29 <dkaratza[m]> ok but for linux there are highly recommended and optional. there are not any mandatory. so I guess the highly recommended become mandatory?

18:32 <dkaratza[m]> or the highly recommended ones go to the optional?

18:52 <dkaratza[m]> ohhh there is also a table for linux but it doesnt render, despite the fact that it exists. so it is not visible either in the documentation

19:21 <hkaiser> dkaratza[m]: not sure what the highly recomended ones are, probably tcmalloc or jmalloc

19:22 <hkaiser> I think those can go into the optional table with a remark that we really recommend using one of them

19:22 <dkaratza[m]> google-perftools hkaiser

19:22 <dkaratza[m]> im talking about this one. where should it go?

19:22 <hkaiser> yah, that's tcmalloc, essentially

19:23 <hkaiser> it's optional, but highly recommended

19:23 <hkaiser> things will work without it, however might be slower

19:25 <dkaratza[m]> alright, its clear now