In what way does adding extra RAM help PC gaming performance?


Recommended Posts

Even i have similar system with even lesser ram (2GB) , will adding more ram help me to get better FPS in Saints row the third? Or is it the processor which is umm bottle-necking ? Even at lowest settings the game is not playable while i see Youtube videos of people having even worse GPU and yet they manage to play it nice on relatively better settings.

It wouldn't necessarily give you higher FPS but the game would be likely to run more smoothly. I'd guess it's likely to be stuttering that's your issue as your CPU and video card are more than the game's minimum requirements.

I don't know why this needs to be repeated time and time again, but there is no valid reason to disable the paging file. It does not increase performance because Windows only pages stuff when it needs to. Let Windows manage your memory, it wouldn't be designed to write a paging file if it didn't think you needed one.

So why are you repeating it then? No-one suggested it as a permanent feature, only to show that a game would max out 4GB of RAM and when you have no pagefile, the system will crash

So why are you repeating it then? No-one suggested it as a permanent feature, only to show that a game would max out 4GB of RAM and when you have no pagefile, the system will crash

Because I like to correct misinformation, I can be a pain in the butt like that.

Because I like to correct misinformation, I can be a pain in the butt like that.

But you weren't correcting misinformation, in-fact you forced me to correct you, the information was correct, there was not even a discussion about disabling the pagefile other than to temporarily do it for a test

Just to add my $0.02 to the discussion.

With regards to turning off the pagefile, I don't like doing it myself. It can SOMETIMES cause windows to go crazy, and some programs expect it to be there. Personally I run with a 1GB pagefile with 8GB of RAM.

The biggest issue that occurs isn't to do with maxing out the RAM I believe. I think its some legacy from when RAM was scarce, but windows loves to page out RAM whenever it can, so even if you are only using 3 of the 4GB you have, then windows will start paging some areas of memory, and you can run into FPS issues.

For the most part, "casual games", (such as LoL or D3) use around 700-1000MB of RAM, and will generally run fine with 4GB of ram (if you're not transcoding lord of the rings, solving the 102385th prime number, and sequencing DNA in the backgound).

I was referring to this post.

I was referring to this post.

Ok well as I brought up the subject of the pagefile, and nothing was quoted in your post I took that as a reply to me

I did experiment with disabling it yonks ago but bad things happened and noticed no improvements either

Ok well as I brought up the subject of the pagefile, and nothing was quoted in your post I took that as a reply to me

I did experiment with disabling it yonks ago but bad things happened and noticed no improvements either

Sorry for the confusion, I should have originally quoted that post

Even i have similar system with even lesser ram (2GB) , will adding more ram help me to get better FPS in Saints row the third? Or is it the processor which is umm bottle-necking ? Even at lowest settings the game is not playable while i see Youtube videos of people having even worse GPU and yet they manage to play it nice on relatively better settings.

Well with 2GB of RAM in general... it's definitely worth upgrading RAM as you WILL notice a difference in overall system performance as i had 2GB myself and then bought a new mobo/cpu/ram and now i am at 8GB and it makes a world of difference as you can run any programs you want and when you exit games the system is still perfectly responsive unlike when you have 2GB it has to reload a ton of data from the hard drive (which system slows down to a crawl during that time) back into RAM before it becomes nice and quick again. even going from 2GB to 4GB would make a clear difference since 2GB your really running on the edge especially when web browsers can burn up 500-700MB pretty quickly where as once you get 4GB that should generally be 'good enough' although depending on what type of RAM you got it's probably a good idea to upgrade to 8GB since DDR3 ram is quite cheap and with 8GB your PC is future proofed as far as RAM goes as with 8GB you can safely assume nothing will really use that much unto the foreseeable future as far as general system use goes and gaming.

but if your on the older DDR or DDR2 RAM still seems to be fairly expensive in which case if you don't want to get a PC i would at least go to 4GB if possible but if you got to 4GB of RAM it's a very good idea to have a 64bit OS otherwise you won't use all of that 4GB of RAM.

i would imagine even in games to some degree you might notice it. but not because of the RAM itself doing it, but because when the game loads from the hard drive it can cause the frame rate to stutter a bit which when you got 2GB of RAM odds are it will be loading from the hard drive fairly often especially on any fancy games.

but as far as that Saints Row thing... if that's a crappy port like GTA4 is that right there ain't doing any favors for your frame rate.

I didn't say Crysis 2, but yea it was up to date when I found out it kills the system with no pagefile, generally when I was causing some big explosions

Clearly that's a problem with the game, hardware / drivers, or OS then.

Clearly that's a problem with the game, hardware / drivers, or OS then.

How is that clearly a problem with all of the above and not the machine running out of RAM ?

The game does not crash with the pagefile enabled, yet it does when it is disabled, the main function of the pagefile is to use the HDD as virtual RAM when the physical RAM is maxxed out

No pagefile, what does the system do when it runs out of RAM? It bluescreens (If you turn off the low memory warning)

With regards to turning off the pagefile, I don't like doing it myself. It can SOMETIMES cause windows to go crazy, and some programs expect it to be there.

I'm not a Windows expert by any measure, but I was under the impression that any allocation of the pagefile/swap is managed by the OS opaquely in such a way that applications don't have to concern themselves with such trivialities. Application heap memory allocation is done though malloc() and friends. I don't see how an application can depend on its (pagefile) presence without breaking the blackbox abstraction that the OS's memory management API provides.

Whenever I've written applications, I've only ever dealt with the malloc interface, and the OS decides if it needs to use disk space due to low memory conditions.

Personally I run with a 1GB pagefile with 8GB of RAM.

That won't be much help if you want to suspend/hibernate though. To be honest, if you're got 8GB of ram, a 1GB pagefile is quite pointless for a few reasons:

1. If you think you're going to run out of memory, and you're burning through 8GB so fast, how is only 1GB going to help?

2. Swapping processes in and out of memory to disk is expensive, in terms of processor resources, energy, and disk longevity.

3. When the OS starts going to the pagefile/swap for all new memory operations, the system is going to crawl to a halt. I can understand if you've only 512MB, 1GB, or even 2GB, but not if you've got 4GB or more. And even then, who's going to want to continue using a system that's relying soley on the pagefile for doing stuff? If you're running out all the time, get more memory, or cut down on the parallel work. I really don't see the benefit of a pagefile for systems with large amounts of memory.

The biggest issue that occurs isn't to do with maxing out the RAM I believe. I think its some legacy from when RAM was scarce, but windows loves to page out RAM whenever it can, so even if you are only using 3 of the 4GB you have, then windows will start paging some areas of memory, and you can run into FPS issues.

That's why I dislike the pagefile in principal. It just slows down the system and uses resources that could be better spent elsewhere. But that's just my opinion, and everybody's entitled to their own :)

I'm not a Windows expert by any measure, but I was under the impression that any allocation of the pagefile/swap is managed by the OS opaquely in such a way that applications don't have to concern themselves with such trivialities. Application heap memory allocation is done though malloc() and friends. I don't see how an application can depend on its (pagefile) presence without breaking the blackbox abstraction that the OS's memory management API provides.

Whenever I've written applications, I've only ever dealt with the malloc interface, and the OS decides if it needs to use disk space due to low memory conditions.

That won't be much help if you want to suspend/hibernate though. To be honest, if you're got 8GB of ram, a 1GB pagefile is quite pointless for a few reasons:

1. If you think you're going to run out of memory, and you're burning through 8GB so fast, how is only 1GB going to help?

2. Swapping processes in and out of memory to disk is expensive, in terms of processor resources, energy, and disk longevity.

3. When the OS starts going to the pagefile/swap for all new memory operations, the system is going to crawl to a halt. I can understand if you've only 512MB, 1GB, or even 2GB, but not if you've got 4GB or more. And even then, who's going to want to continue using a system that's relying soley on the pagefile for doing stuff? If you're running out all the time, get more memory, or cut down on the parallel work. I really don't see the benefit of a pagefile for systems with large amounts of memory.

That's why I dislike the pagefile in principal. It just slows down the system and uses resources that could be better spent elsewhere. But that's just my opinion, and everybody's entitled to their own :)

You need to read up on what the pagefile is for, and what has hibernation got to do with it? What do you think hiberfil.sys is ?

How is that clearly a problem with all of the above and not the machine running out of RAM ?

I'd like to see a screenshot of what you're running, how much memory Crysis is really using, and the BSOD. You were suggesting that running Crysis without a pagefile alone was the cause of a BSOD, and I'm saying, I find it hard to believe the game alone is using that amount of ram, unless it's 1) a bug. 2) you're running other things in the background. 3) You're running mods for the game.

The game does not crash with the pagefile enabled, yet it does when it is disabled, the main function of the pagefile is to use the HDD as virtual RAM when the physical RAM is maxxed out

So you don't notice a visible performance drop when the pagefile starts kicking in then? I've experienced it before, and the system grinds to a halt, especially in games. What I'm saying is, if you're always running out of memory, fine, get some more, but to rely on the pagefile all the time and by doing so degrading system performance, is asinine.

No pagefile, what does the system do when it runs out of RAM? It bluescreens (If you turn off the low memory warning)

On Windows perhaps. I've had low memory warnings on Windows before, but I can't say I've ever seen it blue screen (not to say it doesn't happen).

On GNU/Linux for instance, I've never experienced a total system lockup due to low memory. It's mostly just simple warnings and a few sigsegs.

To disable the pagefile and constantly get out of memory errors is even more asinine. Linux still has swap partitions, and the same thing would happen if you had no swap partition, Linux isn't immune to the physical limitations of computer hardware,

You need to read up on what the pagefile is for, and what has hibernation got to do with it? What do you think hiberfil.sys is ?

Like I said I'm not an expert on Windows. I didn't know Windows uses a separate file for hibernation. I'm used to Linux's swap partition/file which is used for both paging and hibernation/suspension.

To disable the pagefile and constantly get out of memory errors is even more asinine. Linux still has swap partitions, and the same thing would happen if you had no swap partition, Linux isn't immune to the physical limitations of computer hardware,

I don't use a swap partition on Linux either. Never had a need for it. That's just my personal opinion though. I'm not suggesting everyone has to do it.

But I have a question, If you're constantly having to go to the swap because the system is low on memory, isn't it better to just add more memory than degrade system performance by using the disk as a memory substitute?

Haha I'm not entirely sure how this turned into such a heated pagefile debate =P (if someone does want to hear my justifications, feel free to pm me)

If the OP is still here, I would suggest if you can afford the $30, the extra RAM wont harm. Will it make a massive difference? Depends on how you use your computer, it could do (check what your current useage is).

With regards to a pagefile, you can leave it on as any resources it uses to page out RAM is minimal (in the grand scheme of things). If you want to 'live on the edge' you can turn it off - if it all goes pear shaped, turn it back on =)

Haha I'm not entirely sure how this turned into such a heated pagefile debate =P (if someone does want to hear my justifications, feel free to pm me)

I guess it was my fault for bringing it up. Sorry OP :(

I agree with the rest of what you said.

I don't use a swap partition on Linux either. Never had a need for it. That's just my personal opinion though. I'm not suggesting everyone has to do it.

But I have a question, If you're constantly having to go to the swap because the system is low on memory, isn't it better to just add more memory than degrade system performance by using the disk as a memory substitute?

Sure, if you're technically proficient enough to do so, and can afford top of the range hardware. But even on high end systems the OS still swaps data in and out of vmem so obviously it's designed like that for a reason. If your OS is designed to do it, why not get the hint and just leave it alone?

AMD Athlon II X4 620 | Sapphire HD 5770 1GB

Nice system :D

Haha I'm not entirely sure how this turned into such a heated pagefile debate =P (if someone does want to hear my justifications, feel free to pm me)

If the OP is still here, I would suggest if you can afford the $30, the extra RAM wont harm. Will it make a massive difference? Depends on how you use your computer, it could do (check what your current useage is).

With regards to a pagefile, you can leave it on as any resources it uses to page out RAM is minimal (in the grand scheme of things). If you want to 'live on the edge' you can turn it off - if it all goes pear shaped, turn it back on =)

Well I was only going to buy the xtra RAM if it would improve my average framerate in games, but it appears that it will only improve OS performance, loading times, and brief occurances of stuttering in games (pagefile access). Since none of these are really a problem for me, and all I'm looking to do is improve gaming framerates, I'll save the money for a new CPU later on instead. Or maybe I'll just go by an 1/8th and enjoy what I have :rofl:

Why on earth would anyone turn off the page file? I mean, I can understand setting it to a specific size so that it doesn't constantly change size... but turn it off? I mean, doesn't windows do that all on its own? I figure with a few decades of experience programming operating systems for gamers, Microsoft would have included some sort of mechanism to only use the page file when absolutely necessary...

Nice system :D

Well I was only going to buy the xtra RAM if it would improve my average framerate in games, but it appears that it will only improve OS performance, loading times, and brief occurances of stuttering in games (pagefile access). Since none of these are really a problem for me, and all I'm looking to do is improve gaming framerates, I'll save the money for a new CPU later on instead. Or maybe I'll just go by an 1/8th and enjoy what I have :rofl:

Why on earth would anyone turn off the page file? I mean, I can understand setting it to a specific size so that it doesn't constantly change size... but turn it off? I mean, doesn't windows do that all on its own? I figure with a few decades of experience programming operating systems for gamers, Microsoft would have included some sort of mechanism to only use the page file when absolutely necessary...

Because people think that the OS is constantly running from pagefile rather than RAM and thinking that forcing it to run purely in physical memory would make it faster, but as the OS does not run in the pagefile (Not in the sense that a lot of people think it does) it makes no difference, not in a good way anyway

Anyone who wants to read up on it

https://blogs.technet.com/b/askperf/archive/2007/12/14/what-is-the-page-file-for-anyway.aspx?Redirected=true

Gaming is a lot more immersive when it's fluid and smooth. Alleviating loading pauses is just as conducive to smooth gameplay as increasing the framerate. Given that memory is so cheap, it's really a no brainer.

Gaming is a lot more immersive when it's fluid and smooth. Alleviating loading pauses is just as conducive to smooth gameplay as increasing the framerate. Given that memory is so cheap, it's really a no brainer.

Right, but I don't experience the page-file-using stutterfarks that having too little RAM would cause. So as far as I can tell, I have more than enough RAM for all the games that I play, except for, like I said, when I'm flying a jet at mach 1 and it can't load the textures as fast as I can fly. But that is the only case that I can think of when I experience the effects of having too little RAM.

Or is that a VRAM issue?

Right, but I don't experience the page-file-using stutterfarks that having too little RAM would cause. So as far as I can tell, I have more than enough RAM for all the games that I play, except for, like I said, when I'm flying a jet at mach 1 and it can't load the textures as fast as I can fly. But that is the only case that I can think of when I experience the effects of having too little RAM.

Or is that a VRAM issue?

Could be a CPU issue too, I remember RAGE having texture streaming issues

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • I gave the tool a chance the other day to make a USB. An hour later it was stuck at 0% downloaded. I downloaded the official ISO, downloaded Rufus, and made the USB myself in 15 min.
    • <Moved to software discussion and support> I've got fond memories of Winamp. Changing the skins, the different visualisations etc. But now I just need a simple music player. MSN messenger would be another one, MSN Messenger Plus (I think?) offered so many different plugins. But again, it probably wouldn't work for me these days. And then there is miRC. i think it's still going these days, but lord i had fun with that back in the day. Now it's mostly stuff like Discord, WhatsApp group chats, Signal, Telegram... /me is showing his age...
    • ive always been fascinated by old software this is an old video player for windows from apple
    • In the way that you framed it incorrectly. You wrote: "The constant need to close all browser sessions and wait for a new version to install" There's no "constant need to close all browser sessions". That's factually incorrect. The browser downloads its updates in the background and installs them when you open it again. Silently. And there's no "wait for a new version to install", updates are small and take 2-3 extra seconds AT MOST, if any. If you have an SSD, there's zero extra time. Also, every mainstream browser operates this way. Firefox, the FOSS go-to browser, the default on almost every Linux distro, does exactly the same. Also, you don't need to constantly restart Edge for updates to install, you can completely ignore them and it doesn't even ask you to handle them, it's all silent and automatic. So I don't understand what else do you want.
    • DuRoBo Krono Review: Portable E-Ink reader with great ideas that need a bit of improvement by Taras Buria Phone-sized e-readers are gaining traction these days, with more people treating them as a getaway device to cure phone addiction (or at least they are trying to) or having a more pocket-friendly reader that is easier to carry and hold. The market now has plenty of such readers to choose from, and DuRoBo is the latest addition, a new player that offers a more interesting approach to the idea. The Krono is a $279 e-reader with an interesting twist, which tries to make the device more fun and ergonomic. Here is my review. Disclaimer: DuRoBo provided the review sample without any editorial input or pre-approval. The Krono comes in a phone-sized box with pink accents. Inside, you get the device itself, a short user manual, and a USB cable. The cable is a bit old-fashioned, Type-A to Type-C, which is a bit disappointing. Hot take: I would rather have no cable in the box rather than another Type-A cable that gets immediately thrown into my box full of similar cables I never use. The Krono also has no charger in the box, as it relies on accessories you already own, which is fine with me. Here are the specs: Dimensions 154 x 80 x 9.0 mm or 6.06" x 3.15" x 0.35" 173 g or 6.10 oz Materials Black or White plastic Display 6.13-inch E-Ink Carta 1200, 1,648 x 824 pixels, 300 ppi Touch-capacitive. Dual-tone frontlight. Processor 8-core Qualcomm Snapdragon 690 (QTI SM6350) 2 performance cores at 2.07 GHz 4 efficiency cores at 1.71 GHz Memory 6 GB Storage 128GB, non-expandable ~104GB available out-of-the-box Operating system Android 15 with a custom launcher Connectivity Wi-Fi and Bluetooth Battery 3,950 mAh battery Buttons and port USB Type-C port Power button, Volume button, Smart Dial Breathing Lights Audio Mono Speaker and Dual microphones In the box The Krono, a Type-A to Type-C cable, user manual Price $279 on Amazon First impressions Right off the bat, no, this is not a phone replacement. Do not approach this device thinking it can serve you as a dumb phone to cure your TikTok addiction. In addition to the fact that the Krono has no cellular connectivity, I strongly believe that no amount of extra devices can fix your phone addiction until you put some serious effort into it. The Krono is a phone-sized e-reader, a companion for your phone dedicated to reading without distractions. The DuRoBo Krono is made of plastic with a very fine texture. It is hardly premium, but I also cannot say it feels cheap. The device is also a bit thick, quite dense, and well-built without rattling or cracking. You get to choose between two colors: white and black. The front has quite thick bezels, which is hardly surprising for an e-ink device. These things use front light, with LEDs usually placed on the screen perimeter. While I do not mind thicker bezels, the notably larger chin cheapens the look a little. What I mind is a notable seam between the display and the main case, which, after just two days of use, collected plenty of dust and specks. The back of the Krono is what makes the device stand out. There is a cylinder (DuRoBo calls it the Axis) embedded in the back of the reader, housing three elements: a power button on the right edge, a Smart Dial on the left edge, and "Breathing Lights" on the back. An etched DuRoBo logo sits below the cylinder, and it is the only piece of branding you can find on the device. Overall, the design and materials are very unassuming, but the cylinder with additional control elements certainly elevates the look and makes it more interesting. Other physical elements include two microphones (one on the top edge and one on the bottom edge), a USB Type-C port, a volume rocker, and a single mono speaker. There is no fingerprint reader, so if you want to protect your device, a PIN is your only option. The official TPU case is not the most premium-looking Display The Krono has a 6.1-inch E-Ink Carta 1200 touchscreen display with a resolution of 1,648 x 824 pixels (300 ppi). The display is front-lit, and you can adjust the brightness and temperature from cool to warm. Unfortunately, the Krono lacks automatic brightness and temperature adjustments, and you cannot set a custom schedule for the frontlight. However, you can set it to always enable frontlight so that you can see what is happening on the screen when turning it on in a dark environment. On the bright side (get it?), the front light can get extremely dim so that the screen is barely readable in a pitch-dark room. The front light is also uniform across the screen, with no noticeable temperature gradients. I am very susceptible to uneven front light, and it is very easy for me to notice it, but the Krono is doing a very good job in this area. I also like that the edge shadow is not very prominent and barely visible in the black variant. E-Ink Carta 1200 is not the newest generation (there are Carta 1250 and 1300), but it is still a good display. It supports three modes: Clarity, Speed, and Quality. In Clarity mode, text is very sharp and easy to read, but you trade that for more ghosting, a slower refresh rate, and more artifacts when the display changes images. Speed mode, as the name suggests, boosts refresh rate and reduces ghosting, but fine print and text become more jagged. Finally, Quality mode is only available in Android apps. It has the lowest refresh rate, but in return, you get much better visuals, improved gradients, and more. Like brightness and temperature, you can toggle modes from the control center. It is available when swiping from the top-right corner of the screen (the top-left is for notifications). I also like that the Krono can work as a desk clock when not in use. It has a bunch of screensavers, including horizontal clocks with time, date, and current battery level. The screen refreshes once per minute, and battery drain is extremely low (not even 1% in 24 hours). It is a great use of the technology, and another thing I wish more e-ink devices featured. Smart Dial The Smart Dial is Krono's main party trick. It sits on the left side of the device and serves multiple purposes. You can twist or press it to perform various actions, depending on the current use case scenario. When reading books, twisting the dial flips through pages, and pressing it refreshes the screen. On the home screen, the dial adjusts the brightness, and holding the dial pressed launches voice note recording. Finally, a quick double press launches the DuRoBo AI chatbot. While the dial scroll is not notched, it is very smooth and has haptic feedback that confirms your actions, which feels very nice. As a long-term Apple Watch user, I love the idea behind the dial. It feels very natural and oddly satisfying to use, especially with that subtle haptic feedback. I never liked flipping pages with touch input, and I strongly believe each e-reader should come with some sort of physical controls for turning pages. The Krono has both volume buttons (which also work as page turners) and the dial, so you are free to use whichever you prefer. With that said, the dial is not perfect. For one, it sticks out of the case way too far for my liking, raising concerns about durability and longevity when carrying the Krono around in a pocket (it is a pocket-sized device after all). Also, it has too much wobble, which cheapens the experience and makes it feel a bit flimsy and unsecured. While there are two plastic guards on the Krono's case, they are way too small for any kind of protection. I also think DuRoBo should let users customize dial actions (the only available customization is scroll direction), particularly for long and double presses. Not everyone needs voice notes, and DuRoBo AI does not work without an active internet connection, leaving the long press essentially useless when offline. I do not mind these features, and I genuinely think they are useful, but I would rather have the ability to toggle between screen modes, turn the frontlight on/off, or launch my favorite app. I also agree with people on Reddit asking developers to let users adjust the dial sensitivity. I hope this is something DuRoBo can implement with a software update to make the experience more personalized (it is a Smart Dial, after all) and incentivize users to fiddle with the Dial more often. The Dial is a fantastic idea, so please, guys, improve it a little. As for ergonomics, they are mostly fine, but the dial's position may feel a little awkward and way too high. When I use a phone or a phone-sized gadget, I tend to rest one of its corners on my palm for a more secure grip. With the Krono, such a grip is impossible because you cannot reach the dial even with big hands. You have to lower the reader a bit and hold it like a bottle without any extra support for the bottom edge. Such a grip is not necessarily uncomfortable (the Krono is also light enough for it), but it requires a bit of muscle retraining. Sometimes, I do not bother with the dial and hold the Krono like my phone, flipping through pages with volume buttons, as they are perfectly positioned for my right-hand thumb. Interestingly, when testing the Krono, I would often find myself thinking that a roller embedded in the long plastic cylinder on the back of the device would have been a much more comfortable solution. There is a free idea for you, guys. Software The Krono runs Android 15 with a very minimal launcher on top. The home screen presents you with a list of apps, a scrollable list of widgets, and your user profile. Widgets can display time, calendar, or recent books for quick access. You can also add or remove apps from the home screen to keep the most useful stuff around without tapping "Apps." I like this minimalistic approach; it looks clean, easy to understand, and light. I understand that some may find the list of all apps way too clean, but fortunately, DuRoBo lets you switch to traditional icons. The reader also has a bunch of preinstalled apps: Read: The default app for reading. Browser: A Chromium-based browser. Files: A simple file manager. Music: A simple music player. Spark: A voice recorder with transcription support and AI summarization DuRoBo AI: A built-in AI chatbot. Transfer: An app for file transfer over Wi-Fi. If that is not enough, there is the Google Play Store, where you can download all the extra apps you need, alternative readers, podcast apps, chatbots, and more. DuRoBo is not trying to give you an all-in-one device. The standard software experience is quite minimal, which makes it easy to approach and learn. The standard reader supports EPUB, EPUB3, AZW3, MOBI, PDF, TXT, DOC, and DOCX, which is more than enough to let you read most books without third-party software. As for customizing the reading experience, you can select one of five built-in fonts, adjust size and thickness, adjust margins and spacing (only three variants for each), change text alignment and direction, toggle the reading status bar, and switch to dark mode. There is also text-to-speech, which utilizes Android's default TTS tech. While I like the simplistic approach, I cannot help but feel DuRoBo could have made the built-in reader a bit more customizable. However, I am not going to bog down on this, as you can always install any other reader you prefer using the Play Store or by sideloading an APK. Getting books to the Krono is very simple. Given that the device is an Android smartphone without cellular connectivity, you can transfer files via a USB Type-C cable, download them using the built-in browser, share them over Bluetooth, or use cloud storage. My favorite was the built-in Transfer app. It is simple, reliable, and very well-designed. I was surprised by how well-designed the web portal is. It is fast, pretty, and properly categorized. Well done! Once you have your books loaded, you can highlight or underline text, add annotations, bookmark pages, check the table of contents, and ask AI about the selected text. Unfortunately, the Krono has no built-in vocabulary, but again, that is something a third-party reader could fix. Overall, the built-in reader is light and snappy, with just the minimum amount of features for a regular user to enjoy reading books. The Krono has no built-in reading tracking, so stat nerds will have to look for third-party reading apps. However, you can set a daily reading goal, and the reader will notify you when you reach it (for example, one hour). You can also set a reminder to read at a certain time, and when the time comes, the Krono will light up its back LEDs and unlock itself to nudge you. Other than that, the rear LEDs do nothing, not even showing charging progress, which is an unfortunate misopportunity if you ask me. Quirks aside, Krono's Android runs quite snappily and bug-free. Early reviews of the Krono criticized its Android 13-based software quite a lot, but now, the reader runs Android 15, and its software has fixed plenty of initial complaints. I never experienced any issues with built-in apps. AI attempts The DuRoBo Krono comes with a built-in AI chatbot. There is no information on what model powers this thing, but the system says it was "trained by Google." You can launch the bot from the app list or by double-pressing the dial. It works just like any other chatbot, and you can ask it anything by typing or using voice input. The AI saves your chats, and you can rename, export, or delete them. DuRoBo AI requires an active internet connection, and it does not work offline. Its reach and capabilities are also limited. You can only chat in the app and use it in the reader app as a makeshift vocabulary. However, the implementation is kinda awkward. You can only send a selected portion of text to AI without giving it any requests or instructions. I highlighted the word "dumb," and it apologized to me for not being useful. You also cannot ask follow-up questions or send the generated response to a separate chat. The chatbot is also slow, even with fast Wi-Fi, making the overall experience quite frustrating, which makes me again wish for the ability to remap the double press to something else. Spark, the standard voice recording app, also uses AI for note summarization and transcribing. Neither feature works offline, unfortunately. Spark records notes up to 30 minutes using Krono's dual microphones, and you can rename or export notes. Transcription quality is decent, and the speed is alright, but you can find much better solutions in the Google Play Store. What I like about Spark is that transcribed notes are not locked, and you can always type more to elaborate on your ideas, which is handy. Overall, I like that the Krono is not shoving AI down my throat, but to be honest, there is really not that much to shove. AI features here feel raw and need improvements to be more useful. Battery Life Like most E-Ink readers, the Krono has fantastic battery life. Even with a clock as a screensaver, its standby power consumption is incredibly low. And when in use, you can get weeks of reading on a single charge. Without the front light, my unit never sipped more than one or two percent of battery during a one-hour reading session. It was nice to see plenty of battery-related settings. You can limit charging at 80% to protect battery health long-term, check the number of charging cycles, manufacturing/first-time use date, battery health, and the maximum capacity. Additionally, the Krono lets you select what hardware remains enabled when sleeping. This lets you keep Wi-Fi and Bluetooth on (say, if you want to receive notifications, for some reason) and keep audio playing when locked. Turning these features off effectively eliminates any standby battery drain. I left my Krono sitting for 24 hours with a clock screensaver on, and it did not drop a single percent. The pretty big 3,950 mAh battery justifies the device's thickness and ensures you do not have to charge it for long periods. Speaking of charging, it is capped at only 10W, which is a bit disappointing, as getting such a big battery to 100% takes a notably long time in the era of super-fast charging smartphones. DuRoBo Moodi The Moodi is a standalone, optional accessory for your Krono. It is a wireless remote with two customizable buttons that you can use to flip pages, control media, or scroll webpages. The accessory connects via Bluetooth. Despite having a built-in rechargeable battery, it is extremely light. While the Moodi's shape and form factor is not what I would call particularly ergonomic, it is not uncomfortable to hold and use. The Moodi comes with six removable magnetic buttons with various smiley faces. Buttons sit securely, and they have nice-feeling, albeit a little loud, clicks. It is a cute touch that adds a little more fun and character to the device. There is also an accented power button and a single status LED. The latter displays charging status and connection mode. The Moodi supports three modes: Reading: Buttons work as volume buttons, allowing you to flip pages in the built-in reader or other apps that support page turning with volume buttons. Media: Buttons work as skip forward/backward, which is useful when listening to audiobooks, podcasts, or music. Scroll: The third mode lets you scroll pages in the web browser or any other application The Krono properly detects the Moodi and presents you with an on-screen guide when you connect it for the first time (it also displays the battery level). However, you can only change modes by holding both buttons for a few seconds. It is also worth noting that the Moodi works with other devices. I connected it to my iPhone and it let me adjust volume or control media playback. Sadly, the scroll did not work, so you cannot use it to waste time scrolling TikToks. Overall, the Moodi is a cute little accessory, which I can recommend for those who read a lot. It is very useful for remote page flipping when you do not want to burden your hands by holding the Krono all the time. I only wish DuRoBo included a lanyard for the built-in loop. As for the battery life, after using the Moodi for a few days, I only managed to drop several percent of its 90 mAh battery. Despite the small size, it is rated for weeks of use, which is pretty impressive. At $35.99, I cannot say the Moodi is a must-have accessory, but I see the appeal. I prefer using the Krono with its Smart Dial, as I rarely read for more than 40-60 minutes in one sitting. However, if you have a stand and like reading for long periods, the Moodi is the right thing to have. It is a bit more expensive than regular page flippers on Amazon, but it is on par with similar products from Kobo or BOOX. Plus, it has a little more fun to it with removable buttons and better integration into the Krono. Conclusion At the end of the day, DuRoBo Krono is a nice pocket-sized e-reader. Its software focuses on the main things without trying to be everything at once. The smart dial idea is unique and great, and I wish more manufacturers had something similar in their devices. The display is also good, with an even frontlight and "always-on" support. I did not notice any deal-breaking issues with the Krono. However, you can feel that the idea needs some improvements, such as a slightly stiffer dial in a more ergonomic location, perhaps a little more premium materials, and better software customization. I hope the company won't give up on the idea and improve the dial and ergonomics in the second generation. Buy DuRoBo Krono Black - $279.99 on Amazon Buy DuRoBo Krono White - $279.99 on Amazon Buy DuRoBo Moodi - $35.99 on Amazon As an Amazon Associate, we earn from qualifying purchases.
  • Recent Achievements

    • Conversation Starter
      flexorcist earned a badge
      Conversation Starter
    • One Month Later
      AndreaB earned a badge
      One Month Later
    • One Month Later
      agatameier earned a badge
      One Month Later
    • Week One Done
      agatameier earned a badge
      Week One Done
    • Week One Done
      ssd21345 earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      518
    2. 2
      +Edouard
      195
    3. 3
      PsYcHoKiLLa
      147
    4. 4
      ATLien_0
      94
    5. 5
      Steven P.
      77
  • Tell a friend

    Love Neowin? Tell a friend!