Skip to content

2.0.0-1
Compare
Choose a tag to compare
@tanmoysrt tanmoysrt released this 21 May 17:55
· 182 commits to v2 since this release
2.0.0-1
43f55ba
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Hi 👋
Here is the pre-release of Swiftwave v2.
In coming week, will do the final release of Swiftwave v2.

Installation Step

We are working on v2 documentation

In the meanwhile, you can install to tryout Swiftwave v2 by the following steps mentioned here

Then run,

sudo swiftwave init
sudo swiftwave start

// Once setup done, run
sudo swiftwave service enable

Note

Mostly, we have tested on Amd64, Arm64, and ArmV7 (Raspberry pi) architectures running Ubuntu or Debian. You may thus try it out with the pre-release of version 2.

Warning

In Fedora or Centos based distros, you may face that the haproxy is crashing infinitely. To mitigate this set default-ulimits of docker.

  1. Create or edit file /etc/docker/daemon.json and add the default-ulimits. 
    {
   "default-ulimits": {
      "nofile": {
        "Hard": 262144,
        "Name": "nofile",
        "Soft": 262144
      }
    }
}
    Note : Try setting any value in the configuration less than the highest ulimit of the system. To get highest ulimit of system, run ulimit -n -H on your server.
  2. Restart docker daemon of system by systemctl restart docker

What's Changed

Additional Context

After adding many features, still swiftwave takes much less resources.
image
Tested with couple of app builds and deployment
Memory usage stays between 40~75 MB
CPU Usage also stays below 1% most of the time. But, at the time of new server onboarding, it can have 20% of CPU usage. After onboarding completion, CPU usage will decreases below 1%.
P.S : This test has been performed in a 1vCPU 2GB ram Debian server.

Full Changelog: 1.0.0...2.0.0-1

Contributors

fossabot and tanmoysrt
Assets 8
Loading