options with smaller footprint
Is your feature request related to a problem? Please describe. Problem running this on a t2.micro at AWS.
Describe the solution you'd like
simple commands which remove from the docker-compose.yml
geth-monitor-backendandgeth-monitor-frontend; and perhaps also- one miner and one node
Describe alternatives you've considered
several different docker-compose-2nodes.yml, docker-compose-no-ethstats.yml, etc.
Additional context
AWS machines larger than 1 GB RAM cost money, so I restrict my testing to t2.micro as much as possible.
I did not create this project with AWS in mind, but this is an option worth looking into. Even for most development tasks, the monitors are not needed.
Reducing the Node count might not be possible, as the Clique Proof of Authority protocol needs a minimum amount of nodes to work.
Great.
I could actually get it working on a t2.micro when I had removed the monitor dockers,
see https://github.com/drandreaskrueger/chainhammer/blob/master/reproduce.md#results
--> scroll down for (H)
several different ...
docker-compose-no-ethstats.yml, etc.
that seems the easiest way.
It would be ideal if one docker-compose-....yml could import another docker-compose-....yml because then it is safer in case of any future updates (i.e. then not to forget the other file). I haven't had a look whether docker allows for that.
Instead just went for a duplicate, and then removed those 2 containers. Simple.
I think I found something related in the documentation here: https://docs.docker.com/compose/extends/#example-use-case-1
This might also help to clean up the current docker-compose.yml
Edit: Or might not, there is some drama attached to "extends": 🙄 https://github.com/docker/compose/issues/4315
Oh, that sounds/ed great, lol.
It would have been / will be exactly what's needed here, and in several other docker-compose setups that I have been using here for my chainhammer.
Dunno now. Perhaps try out having multiple -f in docker-compose ?
The plan is to enable multiple -f, I am afraid there is no other option.
I would suggest one -f for the monitor and one -f for the docker swarm node
Sounds good
Happy New Year!
Any news about this?
Not urgent!
For now I have simply successfully been still using this old fork https://github.com/drandreaskrueger/geth-dev/commits/master - which is however 18 commits behind your master by now.
I am soon publishing a much automated new version of chainhammer, and then some time later ... I will redo all of the measurements, and shortly before try to make sure that all my external dependencies are on the newest commit.
I am planning to build a new release in the next days, will give this a shot, again!