博客
关于我
强烈建议你试试无所不能的chatGPT,快点击我
ram coe文件_我可以增加页面文件而不购买更多RAM吗?
阅读量:2510 次
发布时间:2019-05-11

本文共 3481 字,大约阅读时间需要 11 分钟。

ram coe文件

ram coe文件

Old hardware often necessitates all manner of work arounds–in this case the question at hand is whether or not increasing the page file can compensate for the failure of a physical RAM module.

旧的硬件通常需要各种解决方法-在这种情况下,当前的问题是增加页面文件是否可以弥补物理RAM模块的故障。

Today’s Question & Answer session comes to us courtesy of SuperUser—a subdivision of Stack Exchange, a community-driven grouping of Q&A web sites.

今天的“问答”环节由SuperUser提供,它是Stack Exchange的一个分支,该社区是由社区驱动的Q&A网站分组。

问题 (The Question)

SuperUser reader IMB poses the following question:

超级用户阅读器IMB提出以下问题:

I’ve a 10+ year old XP PC which surprisingly still works however one of the 256MB RAM finally died. Now I am left with just 256MB. As expected the PC became slower however when I tried to increase the page file to min 4GB max 4GB it become quite fast again to an acceptable level. My question now are:

我有一台10年以上的XP PC,令人惊讶的是它仍然可以工作,但是其中一个256MB RAM最终消失了。 现在剩下的只有256MB。 不出所料,PC变慢了,但是当我尝试将页面文件增加到最小4GB,最大4GB时,它又变得非常快,达到了可接受的水平。 我的问题是:

Will it help if I buy more RAM since the current performance is already acceptable, will it be even faster?

如果因为目前的性能已经可以接受而购买更多的RAM,它会更快吗?

Will just having 256MB RAM but 4GB page file have some implications (maybe the HDD is being pounded or something)?

仅具有256MB RAM但4GB页面文件会带来一些影响吗(也许HDD受到了冲击)?

Can IMB squeeze by with his page-file-workaround (in order to avoid drumming up some expensive vintage RAM)?

IMB是否可以通过他的页面文件替代方法来解决问题(以避免浪费一些昂贵的老式RAM)?

答案 (The Answers)

SuperUser contributor Indrek writes:

超级用户贡献者Indrek写道:

Accessing primary memory (RAM) normally takes in the order of a nanosecond (10-9 s) while accessing secondary memory (hard drive) takes in the order of a millisecond (10-3 s), making RAM access faster by a factor of 1,000,000 times. So to the extent that RAM is actually full and files are getting written to your hard drive’s page file, those operations take 1,000,000 times longer. One would need to check the Task Manager to see what is going on and if RAM is actually full.

访问主内存(RAM)的时间通常为纳秒(10-9 s),而访问辅助内存(硬盘)的时间则为毫秒(10-3 s),使RAM的访问速度提高了1倍。 1,000,000次。 因此,如果RAM实际上已满,并且文件正在写入硬盘驱动器的页面文件,那么这些操作将花费1,000,000倍的时间。 需要检查任务管理器以查看发生了什么以及RAM是否实际已满。

Your decision will depend on what you subjectively deem to be acceptable for the task you are using the computer for. You are certainly not using it for office work?

您的决定将取决于您主观上认为您要使用计算机执行的任务的条件。 您肯定不是将其用于办公室工作吗?

Hans Passants chimes in with some insight into why the computer might feel faster:

汉斯·帕桑斯(Hans Passants)对计算机为何会更快的感觉有所了解:

The only way your machine could have gotten faster is by the paging file getting relocated to a less fragmented part of the disk when you changed its size. A common problem in general on old XP machines. Get a further possible improvement by using a defrag utility first, then run the SysInternals’ PageDefrag tool.

您的机器可以更快地变迁的唯一方法是,在更改磁盘大小时,将页面文件重新定位到磁盘上较少碎片的部分。 通常在旧的XP计算机上存在一个常见问题。 首先使用碎片整理实用程序,然后再运行SysInternals的PageDefrag工具,以获得进一步的改进。

It matters a great deal since you’ll be using the paging file a lot more frequently with this little RAM. A fragmented paging file causes a lot more disk head seeks and that’s slow.

这很重要,因为您将以较少的RAM更频繁地使用分页文件。 碎片化的分页文件会导致更多的磁盘头搜索,而且速度很慢。

For more information about the Windows page file, check out:

有关Windows页面文件的更多信息,请查看:



Have something to add to the explanation? Sound off in the the comments. Want to read more answers from other tech-savvy Stack Exchange users? Check out .

有什么补充说明吗? 在评论中听起来不对。 是否想从其他精通Stack Exchange的用户那里获得更多答案? 查看 。

翻译自:

ram coe文件

转载地址:http://cnjwd.baihongyu.com/

你可能感兴趣的文章
github.com加速节点
查看>>
解密zend-PHP凤凰源码程序
查看>>
python3 序列分片记录
查看>>
Atitit.git的存储结构and 追踪
查看>>
atitit 读书与获取知识资料的attilax的总结.docx
查看>>
B站 React教程笔记day2(3)React-Redux
查看>>
找了一个api管理工具
查看>>
Part 2 - Fundamentals(4-10)
查看>>
使用Postmark测试后端存储性能
查看>>
NSTextView 文字链接的定制化
查看>>
第五天站立会议内容
查看>>
CentOs7安装rabbitmq
查看>>
(转))iOS App上架AppStore 会遇到的坑
查看>>
解决vmware与主机无法连通的问题
查看>>
做好产品
查看>>
项目管理经验
查看>>
笔记:Hadoop权威指南 第8章 MapReduce 的特性
查看>>
JMeter响应数据出现乱码的处理-三种解决方式
查看>>
获取设备实际宽度
查看>>
Notes on <High Performance MySQL> -- Ch3: Schema Optimization and Indexing
查看>>