Skip to content

Avx2 deprecation pt2 #3800

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 5 commits into
base: release/7.6
Choose a base branch
from
Open

Avx2 deprecation pt2 #3800

wants to merge 5 commits into from

Conversation

ggray-cb
Copy link
Contributor

Adding deprecation notice to 7.6. about the requirement for AVX2 instructions on x86 platforms in future server releases.

Preview:

@ggray-cb ggray-cb requested review from malarky and RayOffiah April 17, 2025 15:29
Copy link
Contributor

@RayOffiah RayOffiah left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just a couple of changes.


*_You can reduce the CPU and RAM resources below the Minimum Specifications for development and testing purposes.
[#note1]
^*^You can reduce the CPU and RAM resources below the Minimum Specifications for development and testing purposes.
Resources can be as low as 1 GB of free RAM beyond operating system requirements, and a single CPU core.
However, you must adhere to the Minimum Specifications for production._
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I might be missing something, but where is the opening _ for this footnote?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The original actually just rendered the entire footnote as italic, which is against our style guides. In my opinion, it also makes it hard to read. I had thought about just replacing the footnotes by moving the text someplace else, like a new subheading, or maybe pushing it up before the tables.


Some virtualization environments, such as older AWS EC2 clusters, use the XEN clock source.
This source can cause performance issues because reading it requires an expensive system call to the hypervisor.
In some cases, a XEN clock source has used up to 25% of CPU time when timers are in heavy use.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Blimey! As much as that??

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That's from the original docs... I don't have any contradictory numbers, so I'll just keep it. For what it's worth, ChatGPT also seemed a bit surprised.

ggray-cb and others added 2 commits April 18, 2025 08:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants