https://en.m.wikipedia.org/wiki/Constraint_Handling_Rules
It’s like prolog without the performance overhead thanks to the magic of linear logic.
Anyway, the last time I needed to write a constraint solver in Prolog, I did try it in CHR, but it was way too slow for my needs, so I ended up rewriting it in plain SWI-Prolog. So from this one data point, I don't see where your assertion of "without the performance overhead" comes from.
I also found CHR's multiset semantics quite painful for my application, a lot of my rules had to be careful not to post duplicates of constraints. I would have loved having a single flag for telling the CHR system to just take care of that for me. That would have cleaned up my model and probably been more efficient as well. All of the above is qualified by the fact that I was a relative CHR newbie at the time.
Overall: CHR is quite interesting, but it's no magic silver bullet, and you seem to be overselling it.
I like the idea though that time in programming languages is the root of very much evil. That is, the programmer must spend time thinking about what order to put the statements.
In many cases the order does not matter so it is wasted cognitive effort. In some cases it matters a great deal.