-
-
Notifications
You must be signed in to change notification settings - Fork 2.9k
add script to generate a example folder for collecting many files #4240
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
add script to generate a example folder for collecting many files #4240
Conversation
|
Not sure if this is a good idea, that many files does incur an overhead for checkout doesn't it? |
blueyed
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I also do not like it. While it might be small in Git it still uses inodes etc, and adds unnecessary noise.
Instead, there should be a script to generate this, and maybe a Makefile around it, which then could grow into a performance/benchmark test suite.
|
we totally need some tooling around manual testing support (this would be a manual test where we want to drop into a optional manual interaction point with a ipython shell or a system shell in the testdir then we could jsut start some tests in "interactive mode, and mess around |
|
@RonnyPfannschmidt |
|
@blueyed i dislike incomplete error prone tooling because ^^ - and i absolutely refuse makefiles - those things should die already |
|
I concur with @RonnyPfannschmidt that Makefiles are not the way to go. 😁 I propose we commit a Python script which can generate the files; this way we don't incur the overhead of 1000s files on each checkout, plus the script can be configurable (how many files to generate, and depth of folders, etc) which will make it even more useful in the future (say we want to test with 10k or 100k files, 6 directories deep). I think the script can reside inside the examples folder, say in |
|
@nicoddemus good thinking |
721a850 to
bfa1993
Compare
Codecov Report
@@ Coverage Diff @@
## master #4240 +/- ##
==========================================
+ Coverage 93.38% 95.87% +2.48%
==========================================
Files 109 109
Lines 24585 24590 +5
Branches 2389 2392 +3
==========================================
+ Hits 22959 23575 +616
+ Misses 1308 720 -588
+ Partials 318 295 -23
Continue to review full report at Codecov.
|
|
@nicoddemus And a Makefile would just call the script then, preparing the files needed for the perf tests, but it would not be required to be used of course. I am not talking about autoconf or something similar, but just something basic as (in collect_stats): 100x10:
python generate_files.py 100 10 $@
test: 100x10
cd 100x10 && pytest -k doesnotmatchThen CI / perf generation could use Anyway, this was just an idea for the future, but the main point is that files should be generated dynamically, not being committed, and I am glad you agree. Closing this PR then. |
|
Nice work! 👍 |
No description provided.