yup, wontfix.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/392#issuecomment-372293010___
Rpm-maint mailing list
Closed #392.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/392#event-1516097945___
Rpm-maint mailing list
Then you are stuck: it's your workload, not the rpmspec parser implementation,
that is the root cause.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
If I would be querying them sequentially, then it would take hour or so
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
> Since your program appears to be multithreaded, try splitting the 4000
> specfile queries across 10-20 worker threads.
That's exactly what it does.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
@n3npq it's not single spec.. Its 4000+ different specs.
What I wrote there if you run `rpmspec`, then tool is taking 2 minutes to do
the job. If you remove execution of rpmspec, then tool takes 3 seconds.
--
You are receiving this because you are subscribed to this thread.
Reply to this email
@n3npq believe me, it is slowest part in my tool ;)
```
287.25user 152.95system 2:11.94elapsed 333%CPU (0avgtext+0avgdata
68724maxresident)k
13648inputs+0outputs (53major+30349595minor)pagefaults 0swaps
```
```diff
diff --git a/src/main.rs b/src/main.rs
index 4b0f2ff..9306517 100644
---
Um, spec file parsing is not exactly slow (even with lightly used %include) and
there already is a means to query EVR from a spec file.
Presumably you are seeking the EVR used on every %changelog entry by brute
force: try being more clever, by (say) pickling a store in the git directory