August 11, 2025 at 9:48 am
Hi everyone,
I’d like to share something from the science side of life rather than the SQL side. It’s called the NKTg Law on Varying Inertia.
In classical mechanics, Newton’s laws describe how objects move under the influence of forces. But the NKTg Law takes a different angle: instead of focusing only on forces, it looks at the relationship between position (x), velocity (v), and mass (m) — with m allowed to change over time — to describe an object’s movement tendency.
The core idea is:
p = m × v # momentum
NKTg₁ = x × p # position × momentum
NKTg₂ = (dm/dt) × p # mass change rate × momentum
How to interpret it:
NKTg₁ > 0 → the object tends to move away from a stable state.
NKTg₁ < 0 → the object tends to move toward a stable state.
NKTg₂ > 0 → mass change supports the movement.
NKTg₂ < 0 → mass change resists the movement.
A stable state here means a situation where position, velocity, and mass balance out to maintain a controlled motion pattern.
I find it interesting to think about this not only in physics but also as a metaphor — for example, in project management, workloads, or even personal productivity:
“Mass” could be the amount of work or data you’re dealing with.
“Velocity” could be your processing speed.
“Position” could be how far you are into your goal.
And the two NKTg values might tell you whether you’re getting closer to stability or further away.
I’m curious:
Have you ever seen similar “momentum” or “tendency” models in non-physics fields?
Could this type of thinking be applied to systems, teams, or even SQL Server performance monitoring (just for fun)?
Looking forward to hearing your thoughts!
August 11, 2025 at 3:26 pm
Just because I was curious, I looked into this and I am a bit skeptical on it.
I found this website with more information on it:
Where some assumptions are being made about the mass change being constant even though it isn't. Mass changing over time isn't a constant value, so while models like this are good at estimating the future state, you are not taking into account the factors that attribute to mass change and thus the mass change calculation is incorrect UNLESS it is a constant. We can see from the data that mass chance is NOT constant on the planet in that example and actually went up somewhere between 2023-12-31 and 2024-01-01 and for the duration of 2024. Due to the mass not changing, the calculation for NKTg2 would be 0 and now the model doesn't work. You can confirm this by using data from 2024 to predict 2025 and due to the mass not changing. The model you propose requires the mass to change. The model also requires you to know the location (x) and velocity (v) in order to calculate NKTg1. The website I found seems to only be predicting the mass over time and predicting it wrong.
I also do not see how this changes anything with Newton's laws. NKTg1 is just saying that if an object is in motion, it will remain in motion, which we already know from Newton's laws of motion. NKTg1 doesn't factor into the equation any other forces acting on the object. NKTg seems to rely on data extrapolation assuming no change in forces. If I tell you that a baseball is at location 123m and it has a velocity of 10 m/s at a 45 degree angle perpendicular to the Earth, your model would say it keeps going up which we know is not true. Even if we add more data points, the model doesn't account for change in velocity - only change in mass and the baseball shouldn't be changing mass.
Now as for momentum or tendency models in non-physics fields, it happens all the time. Stock prices are based entirely on data extrapolation to guess which stocks will behave well based on past and current behavior. SQL Monitoring tools do this with estimating when disks or databases will be full. Any report that does data extrapolation does this sort of stuff. I've done similar things in Excel with my estimated vacation and sick time for example.
The NKTg is also adding 2 statistically insignificant numbers - NKTg1 comes in at 10^36 while NKTg2 comes in at 10^22. That could EASILY be a rounding error when calculating NKTg and in the example provided, NKTg1 = NKTg. Reviewing the link I provided, I don't really see what it is even calculating - we can see what NKTg works out to be, but what is that value used for? It's not used to calculate the position (x), mass, or velocity - it looks like the model just extrapolates data and then throws on extra math for... fun?
Not trying to shoot down the study or the "law", I just don't really see what it is doing that isn't already covered by Newton's laws of motion, except it seems to be introducing error.
The above is all just my opinion on what you should do.
As with all advice you find on a random internet forum - you shouldn't blindly follow it. Always test on a test server to see if there is negative side effects before making changes to live!
I recommend you NEVER run "random code" you found online on any system you care about UNLESS you understand and can verify the code OR you don't care if the code trashes your system.
Viewing 2 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply