On accounts with only a handful of notes, speed improved by 2x or more. So how fast are we talking? We put Evernote Web to the test. Not only did this make the downsync process incredibly fast, but it unlocked important synergies between Evernote Web and the other clients. To solve this problem, we updated the Web’s storage system from IndexedDB to SQLite/WASM, SQLite’s web-compatible product. And given that some customers have tens of thousands of notes, it’s clear how the whole process might take an infuriatingly long time. The more notes in a customer’s account, the greater the number of records. ( Customer records can refer to notebooks, reminders, notes metadata, preferences, widgets, and other important Evernote components.) That meant each customer record had to be downloaded, processed, and stored individually. Unlike Evernote Desktop and Mobile, which use a storage system called SQLite, Evernote Web used IndexedDB-a system that didn’t allow for records to be retrieved in bulk. We’re delighted with the results-and we’re sure Evernote customers will be, too! With speed on our minds, we set out to make the downsync process much snappier. Each one kicks off a process called an initial downsync, during which all the user’s content is re-downloaded into the browser’s storage system so the user can access their Evernote notes offline.įor the largest Evernote accounts, the entire initial downsync process took up to ten minutes (which is at least nine minutes too long!). Deleting the cache…Īll of these are routine activities that every Evernote Web user is familiar with. Reloading the page following an expired session.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |