You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This library is awesome for integration testing -- many thanks.
One thing that I have noticed is that most tests can run much faster if the docker tmpfs feature is used when running a container. For instance, on OSX one test went down from 40 seconds to 10 seconds when the database was run in tmpfs.
Using tmpfs is done through the HostConfig part of the docker API.
Would it be possible to support the tmpfs option in docker-it-scala?
The text was updated successfully, but these errors were encountered:
Many thanks, this works great and gave the performance increase we were expecting.
In case anybody is reading this in the future, this is how to use tmpfs:
// Run the app on tmpfs -- this improves peformance especially on OSXvalhostConfig=HostConfig(tmpfs =Some(Map("/YOUR/mountpoint/here"->"rw,size=250M")))
// Then add hostConfig when creating the docker containervalmyContainer=DockerContainer(containerName)
.withPorts(MyPort->None)
.withReadyChecker(
DockerReadyChecker.LogLineContains(
"Your ready checker here"
)
)
.withHostConfig(hostConfig)
This library is awesome for integration testing -- many thanks.
One thing that I have noticed is that most tests can run much faster if the docker tmpfs feature is used when running a container. For instance, on OSX one test went down from 40 seconds to 10 seconds when the database was run in tmpfs.
Using tmpfs is done through the HostConfig part of the docker API.
Would it be possible to support the tmpfs option in docker-it-scala?
The text was updated successfully, but these errors were encountered: