# Installation of CCX\_2.23 fun

**URL:** <https://calculix.discourse.group/t/installation-of-ccx-2-23-fun/3833>\
**Category:** Getting started\
**Created:** [March 19, 2026, 10:35pm UTC](https://calculix.discourse.group/t/installation-of-ccx-2-23-fun/3833 "2026-03-19T22:35:00Z")\
**Posts on this page:** 1\
**Showing post:** 18

<div class="post-metadata">

**Author:** ![JuanP74](https://avatars.discourse-cdn.com/v4/letter/j/b5a626/32.png) [@JuanP74](https://calculix.discourse.group/u/JuanP74)\
**Post date:** [October 21, 2026, 5:00pm UTC](https://calculix.discourse.group/t/installation-of-ccx-2-23-fun/3833/18 "2026-10-21T17:00:34Z")

</div>

could you elaborate a bit more on your answer…what I found about it is this: ["correction to SPOOLES.2.2 for large input decks" - #3 by feacluster](https://calculix.discourse.group/t/correction-to-spooles-2-2-for-large-input-decks/1047/3)

and the bottleneck I identified isn’t PARDISO but ARPACK. I case you were talking about the i4 and i8 issue, both versions I have have PARDISO as solver, one compiled as i4 and another as i8 (both from @feacluster), in my linux system i8 version runs slower for the same problem, in windows 11 it’s almost the same

---

_[View the full topic](https://calculix.discourse.group/t/installation-of-ccx-2-23-fun/3833)._