export TZ=Asia/Tokyo # to set timezone for single terminal [Click]
Explained about Virtual Memory and Hows it works with Block diagram
https://www.cs.uic.edu/~jbell/CourseNotes/OperatingSystems/9_VirtualMemory.html
https://www.digitalocean.com/community/tutorials/atop-command-in-linux
Useful option:
atop
atop -m
UDP Packet tcpdump and print message:
tcpdump -i ens192 -nnvv -A udp port 5060 -s0 #this will print with ttl info
tcpdump -i ens192 -nn -A udp port 5060 -s0 # this just print packet content
UDP Send Message:
echo -n "hello" >/dev/udp/remoteIpAddr/5060
Found an interesting JVM Flag :
java -XX:+UnlockDiagnosticVMOptions -XX:+PrintFlagsFinal -versionIt prints hundreds of various options, I never heard about before. It also prints default values, that helps diagnose JVM behaviors better. Another interesting flag is:
-XX:+UnlockExperimentalVMOptionsOther JVM Flag :To trigger heap dump on out of memory, you can use-XX:+HeapDumpOnOutOfMemoryError This JVM option produces a stack dump when your JVM dies with OutOfMemory Error. There is no expense involved unless an OOM really occurs. This flag is a requisite for production systems as it is usually the only way to determine the problem deeply. The heap dump will be set up in the “current directory” of the JVM by default. If you wish to create heap dumps on specific directory, then run -XX:HeapDumpPath= [path-to-heap-dump-directory] -XX:+UseGCOverheadLimit -XX:OnOutOfMemoryError="< cmd args >;< cmd args >"If we want to restart the server immediately after out of memory occur, then we can
set this parameter of the same purpose –XX:OnOutOfMemoryError="shutdown -r"
#1. resolving the conflict in bit bucket pull request
git checkout commit-id
eg:
$git branch -a
* (HEAD detached from eb9e6ce)
master
test
remotes/origin/HEAD -> origin/master
remotes/origin/master
remotes/origin/test
#2. merge the changes from master to the detached HEAD,so both changes will be there if conflict
git merge remotes/origin/master
HEAD>>>>
<<<<<<
#3. resolve the conflit and commit it ....
git add files
git commit -m "conflict resolved" # status shows (HEAD -> test)
#4. Pushing the commit to the remote and switch to the target branch and pull
git push origin HEAD:refs/heads/test
git checkout <branch-name>
git pull #status shows conflict fixed (HEAD -> test, origin/test)
#5. In bit bucket the master changes will be sync to the test branch

RX_queue_number = hash('192.168.254.30', '192.168.254.1', 65400, 4321) % number_of_queues
ethtool. On our setup it is:receiver$ ethtool -n eth2 rx-flow-hash udp4
UDP over IPV4 flows use these fields for computing Hash flow key:
IP SA
IP DA
RX_queue_number = hash('192.168.254.30', '192.168.254.1') % number_of_queues
ethtool we can select the tuple (src IP, dst IP, src port, dst port) for hashing:receiver$ ethtool -N eth2 rx-flow-hash udp4 sdfn
Cannot change RX network flow hashing options: Operation not supported
send syscall, it wouldn't be efficient. Context switches to the kernel have a cost and it is be better to avoid it. Fortunately a handy syscall was recently added to Linux: sendmmsg. It allows us to send many packets in one go.SO_REUSEPORT each of the processes will have a separate socket descriptor. Therefore each will own a dedicated UDP receive buffer. This avoids the contention issues previously encountered:receiver$ taskset -c 1,2,3,4 ./udpreceiver1 0.0.0.0:4321 4 1
1.114M pps 34.007MiB / 285.271Mb
1.147M pps 34.990MiB / 293.518Mb
1.126M pps 34.374MiB / 288.354Mb

SO_REUSEPORT layer.ethtool -S [interface]tc qdisc show dev [interface]tc command to manipulate the available multiqueue parameters. Without knowing your intentions, it's difficult to give a specific answer, but this information should get you pointed in the right direction./proc/net/softnet_stat file with the softnet.sh script:
iptables -t filter -A INPUT -s 59.45.175.62 -j REJECT
-t switch specifies the table in which our rule would go into — in our case, it’s the filter table. The -A switch tells iptables to “append” it to the list of existing rules in the INPUT chain. However, if this is the first time you’re working with iptables, there won’t be any other rules, and this will be the first one.-s switch simply sets the source IP that should be blocked. Finally, the -j switch tells iptables to “reject” traffic by using the REJECT target. If you want iptables to not respond at all, you can use the DROP target instead.iptables -A INPUT -s 59.45.175.62 -j REJECT
iptables -A INPUT -s 59.45.175.0/24 -j REJECT
-d flag to specify the destination IP:iptables -A OUTPUT -d 31.13.78.35 -j DROP
iptables -L --line-numbers
iptables -D INPUT -s 221.194.47.0/24 -j REJECT
iptables -F INPUT
mysqldump -u root -p --no-data dbname > schema.sql
# create swap file of 512 MB
dd if=/dev/zero of=/swapfile bs=1024 count=524288
# modify permissions
chown root:root /swapfile
chmod 0600 /swapfile
# setup swap area
mkswap /swapfile
# turn swap on
swapon /swapfile
apt-get install python-matplotlib