# Cores=x doesn't impact the number of cores actually used

**URL:** <https://discourse.pymc.io/t/cores-x-doesnt-impact-the-number-of-cores-actually-used/9946>\
**Category:** v5\
**Created:** [July 19, 2022, 9:10am UTC](https://discourse.pymc.io/t/cores-x-doesnt-impact-the-number-of-cores-actually-used/9946 "2022-07-19T09:10:14Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![ozika](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.pymc.io/ozika/32/4295_2.png) [@ozika](https://discourse.pymc.io/u/ozika)\
**Post date:** [July 19, 2022, 9:10am UTC](https://discourse.pymc.io/t/cores-x-doesnt-impact-the-number-of-cores-actually-used/9946/1 "2022-07-19T09:10:14Z")

</div>

Hi,

`bambi==0.9.0.`  
`pymc==4.0.0`

I have an issue similar to [#187](https://github.com/bambinos/bambi/issues/187) - no matter what the number of cores is in the `fit()` (bambi) / `sample()` (pymc) method the process utilized maximum number of cores on my computer.

For example, here I specified `cores=4`.

 ![Screenshot from 2022-07-18 09-24-33](https://canada1.discourse-cdn.com/flex036/uploads/pymc3/original/2X/e/e1d70894d49d10146f825d281365e27edaf7855a.png)

Now, I suspect that this relates to [this debate](https://discourse.pymc.io/t/regarding-the-use-of-multiple-cores/4249/2) but I am still not sure how can one restrict the actual amount of comp resources used. Any pointers? Thanks!

P.S.: This jams up the pc, so I have to run even smallish models on HPC which isn’t super practical.  
P.S.II: See also [this issue](https://github.com/bambinos/bambi/issues/547) for ref.

---

<div class="post-metadata">

**Author:** ![fonnesbeck](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.pymc.io/fonnesbeck/32/13_2.png) [@fonnesbeck](https://discourse.pymc.io/u/fonnesbeck)\
**Post date:** [July 20, 2022, 1:55pm UTC](https://discourse.pymc.io/t/cores-x-doesnt-impact-the-number-of-cores-actually-used/9946/2 "2022-07-20T13:55:17Z")

</div>

Can you replicate this on a pure PyMC model (no bambi)?