![]() For my initial uploud it meant over 140k+ writes on SSD so my wearout factor of SSD went a little bit down. On my SSD drive it means, that editing record for every file means creating journal file, writing necessary data into it, than commit the data into main database = at least 2 writes for every change. ![]() The minus is that every change on client is done via separate journal file. ![]() So you can see its database structure and data. I dig into that a bit deeper, but only found a hint, that this constant 12288 bytes is from old microsoft windows phone 7.x development framework.ġc) SQL Lite based database – this one is minus and plus (see my point 1d) ), the client uses for its internal workings SQL Lite database, which can be accessed in its pure form via any db tool. I was uplouding a large collection of files (70k+) so the noise from hdd lasted for several days. So instead of one long read, it does zillions of reads, with many reads needing a disk to seek. What i found? That the app is reading my files in this way: It opens file at some current location, reads 12k (12288B) in one read, then performs another 4k read and then closes the file. The sync also meant all the problems described bellow to reappear again.ġb) the client is baddly written app – i noticed, that my hdd was doing some strange noises during intital uploud, so i monitored it with SysInternals ProcMon. I mean seriously, i expected, that there will be NO CHANGE TO MY FILES AT ALL, but this?īut, if file timestamp is not an issue for you, than you might consider this as a no problem. The client app suddenly showed (by number of files to sync) that all those restored files need to be synced, and only change it did to them was to change the file timestamp (probably “restored” from cloud). I restored my files from backup from before i went online, it seemed ok for one week or so, the client DIDN’T detect any change, but then again. WTF? It did on almost all of my files, but not all, the key to what files get this behaviour and which not is completelly unknown to me. I noticed that after a “30 days no ask money back period” □ The client is changing almost all file changed timestamps (the date when the file was changed for last time) to a date and time, when the file was uplouded to the service. I mean, i personally want to go away from this service and woun’t recommend it at all for this one. I’ve encountered several problems with 1) the client, 2) with the web interface, 3) the security:ġa) THE WORST THING – FILE TIMESTAMP CHANGE !!!! (WTF!!!!) – This one really got me. The windows client is really simple – install, pick a folder and let the app to do all the necessary things. For 25$ a year it seemed quite reasonable. The basic thing i went for this service (my first cloud based backup storage) was the price. I’m using mediafire for 2 months and it can still surprise me with new quirks to its working. What did you think about this MediaFire review? What features would MediaFire need for you to sign up for an account? Let us know in the comments. In short: MediaFire is that friend you don’t mind being at your party, but you don’t care if you forget to invite them, either. There are plenty of other, better cloud service options, such as, pCloud and Icedrive. It’s difficult to recommend MediaFire when it doesn’t offer more than similar cloud storage providers. Also, the poor customer support should be a cause for business users to look elsewhere. MediaFire may lure in businesses, but there’s not much on offer. MediaFire’s knowledgebase covers the basics, like how to upload and download files, but it’s lacking beyond that. We’ve yet to receive a response after four working days, which doesn’t put the support team in a good light. We raised a support ticket with MediaFire, asking what type of encryption it uses to protect files. Users can access a knowledgebase to get answers to basic questions. MP4 Repair: How to Fix Corrupted Video Files in 2019. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |