-
Notifications
You must be signed in to change notification settings - Fork 115
Issues with test project #46
Comments
Sorry about the Eidolon issue, was going to fix it last week but got swamped with other work. Eidolon is probably not the best project to use, but it is a large-scale codebase that's used in production, and approximates a real-world use case for a lot of devs. While external dependencies can cause issues, they also represent a common pattern for development. Additionally, eidolon is a "stable" project with very few planned changes. Here's the commit graph: I understand your reservations, but this wasn't a resource I ever planned on making scientific (there are other metrics for that, like Geekbench). It was just a way for developers to compare what relative build times look like across different machines. I'll try to fix the Eidolon failures on Monday. Thanks for contributing! |
Was about to say... why can't we use a proper/plain Xcode project for this. Jumping through 10 hoops to install this crap, including asking for a Github user/password. No sir-io, thank you :) Something like a stable
|
@eaigner I used this project because this is the project I had two and a half years ago. It's a real-world, in-production app that exemplifies the kind of work that I do day-to-day. If you don't like it as a benchmarking app, you're free to go start your own Xcode performance-benchmarking project. |
Wanted to post results of my two macs, but could get the test project to build because of this issue.
Is this really the best project to do benchmarking on as it requires so many dependencies which can lead to multiple issues? Also, the eidolon project is constantly updated, which can affect build times making results incomparable.
My suggestion would be to add a test project to this repo which doesn't use any 3rd party dependency, is easy to setup and is never changed. This would probably lead to more contributors.
The text was updated successfully, but these errors were encountered: