# Prolog uses only 13% of CPU and takes an hour to complete

**URL:** <https://swi-prolog.discourse.group/t/prolog-uses-only-13-of-cpu-and-takes-an-hour-to-complete/2673>\
**Category:** General\
**Created:** [July 21, 2020, 9:14pm UTC](https://swi-prolog.discourse.group/t/prolog-uses-only-13-of-cpu-and-takes-an-hour-to-complete/2673 "2020-07-21T21:14:41Z")\
**Posts on this page:** 1\
**Showing post:** 20

<div class="post-metadata">

**Author:** ![EricGT](https://avatars.discourse-cdn.com/v4/letter/e/f1d935/32.png) [@EricGT](https://swi-prolog.discourse.group/u/EricGT)\
**Post date:** [August 5, 2020, 3:19pm UTC](https://swi-prolog.discourse.group/t/prolog-uses-only-13-of-cpu-and-takes-an-hour-to-complete/2673/20 "2020-08-05T15:19:53Z")

</div>

> [@edsolem](#):
>
> Now that I am taking the doc. at its word

[Here](https://swi-prolog.discourse.group/t/building-a-port-scanner/2580/25) is my backstory of first using concurrent\_forall/2,3.

The entire [topic](https://swi-prolog.discourse.group/t/building-a-port-scanner/2580) is an interesting read as it has woven into it discussion of the predicates related to concurrency and threads.

HTH

---

_[View the full topic](https://swi-prolog.discourse.group/t/prolog-uses-only-13-of-cpu-and-takes-an-hour-to-complete/2673)._