I put an introduction a few emails down, but to recap my name is Sam, I'm a 
college freshman, and I'm very interested in working on improving Sympy's 
benchmarking services over this summer through GSOC.  

While going through the project description I had a few questions:

1) *"It also needs an automated system to run them"*
What exactly is meant by this.  Right now, github actions seems to be 
already automatically running benchmarking after each pr.  Why is this not 
an automated system?  Is the meaning of automated system something that 
runs weekly/monthly on the whole repo, generates a benchmark report and 
sends it* somewhere?*

2) *How to go about hosting benchmarks on a remote, dedicated machine?*  
What's the general idea of how to go about this in open source project.  Is 
there money available to pay some cloud provider to host it?  Free hosting 
options?(doesn't seem reliable enough for benchmarking).

3) *SymEngine vs SymPy.  *I'm not familiar with SymEngine.  Approximately 
how similar are SymPy and SymEngine?  Is making the project also work with 
SymEngine more of a quick fix(≈1-2 weeks) or should I expect it to take 
longer?

4) *Current Benchmark Suite*
*"We currently have a benchmarking suite and run the benchmarks on GitHub 
Actions, but this is limited and is often buggy"*
 
What are the limitation(s) to github actions that this project should 
address?
If we don't use github actions, is there another way to make it run after 
every PR like we have now?

5) *Where are the tests run now?*
On the project description it says " the results are run and hosted Ad 
Hoc", which I assumes means whatever computer is running all the other PR 
tests.  Just want to make sure this is correct.


-- 
You received this message because you are subscribed to the Google Groups 
"sympy" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sympy/ed7520ea-3fee-4185-b087-0a3a38dd763fn%40googlegroups.com.

Reply via email to