I (any many collegues here) have been caught several times by the
following example:
1. did something in parallel on a cluster, set up via
parallel::makeCluster().
2. e.g. allocated 20 cores and got them on one single machine
3. ran some code in parallel via parLapply()
Bang! 400 threads;
So
To whom are you addressing this question? The OpenMP developers who define the
missing-OMP_THREAD_LIMIT behaviour and-or supply default config files? The CRAN
server administrators who set the variable in their site-wide configuration
intentionally or unintentionally? Or the package authors expe
Hi Uwe,
I agree and have also been burnt myself by programs occupying the maximum
number of cores available.
My understanding is that in the absence of explicit parallelisation, use of
data.table in a package should not lead to this type of behaviour?
Best,
Scott
On Wed, 23 Aug 2023 at 14:30,
On 23.08.2023 15:58, Jeff Newmiller wrote:
To whom are you addressing this question? The OpenMP developers who define the
missing-OMP_THREAD_LIMIT behaviour and-or supply default config files? The CRAN
server administrators who set the variable in their site-wide configuration
intentionally
I think one should be very cautious about overriding "standard" mechanisms for
controlling software infrastructure like OpenMP. You risk making the task of
navigating the already-complex task of configuring the software environment
even more complex by increasing the number of places you have t
When I invoke valgrind via
R -d valgrind -e '...'
the options in the file ~/.valgrindrc are being picked up. Good.
When I invok valgrind via
R CMD check --use-valgrind ...
the options in the file ~/.valgrindrc are NOT being picked up. Bad.
And valgrind complains. How can I add the needed
On 23/08/2023 2:54 p.m., Dirk Eddelbuettel wrote:
When I invoke valgrind via
R -d valgrind -e '...'
the options in the file ~/.valgrindrc are being picked up. Good.
When I invok valgrind via
R CMD check --use-valgrind ...
the options in the file ~/.valgrindrc are NOT being picked up. Ba
On 23 August 2023 at 16:49, Duncan Murdoch wrote:
| On 23/08/2023 2:54 p.m., Dirk Eddelbuettel wrote:
| >
| > When I invoke valgrind via
| > R -d valgrind -e '...'
| > the options in the file ~/.valgrindrc are being picked up. Good.
| >
| > When I invok valgrind via
| > R CMD check --us
