Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.mobile.android > #37071
| From | Daniel James <daniel@me.invalid> |
|---|---|
| Newsgroups | comp.mobile.android |
| Subject | Re: Android 6 |
| Date | 2016-12-31 13:27 +0000 |
| Organization | A noiseless patient Spider |
| Message-ID | <VA.00000c24.0503f376@me.invalid> (permalink) |
| References | (5 earlier) <f956805f-b339-fe10-b20a-faed1ff0ff49@arnowelzel.de> <291220161202474716%nospam@nospam.invalid> <a9d5f932-7b61-0ec9-6954-ac9f7f27c7bb@arnowelzel.de> <VA.00000c22.00519969@me.invalid> <bad4a6af-a0df-3671-b8e8-589eb15e0b4d@arnowelzel.de> |
In article <bad4a6af-a0df-3671-b8e8-589eb15e0b4d@arnowelzel.de>, Arno Welzel wrote: >> As a flash card gets full the write process will become slower >> as more data typically needs to be moved around by the >> wear-levelling algorithms to make room. That's not particularly >> dependent on the filesystem in use, but will be a factor on any >> device. > > I talk about READING data and "nospams" claim that FAT based systems > get slower with in increasing number of files. Yes, ... and I'm trying to analyse how/why that might seem to be the case. As I said: a card may get slower as it gets full, but that's NOT something that only happens with FAT. >> SSDs that support the low-level TRIM command are less susceptible to > [...] > > Did you even read the thread so far? The point is that where TRIM is supported the slow-down when a card gets full will be less, because of the information provided by TRIM. If the card supports TRIM but the FAT filesystem driver doesn't, then the benefit of TRIM won't be seen if the card is formatted with FAT. In that case (but AFAICS *only* in that case) "nospam" may be correct. However, I doubt the flash controllers in most micro-SD cards (unlike big SSDs with e.g. SATA interfaces) typically support TRIM. -- Cheers, Daniel.
Back to comp.mobile.android | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Android 6 Bill <Billaboard@gmail.com> - 2016-12-22 17:21 +0000
Re: Android 6 The Real Bev <bashley101@gmail.com> - 2016-12-22 10:00 -0800
Re: Android 6 Bill <Billaboard@gmail.com> - 2016-12-23 00:23 +0000
Re: Android 6 nospam <nospam@nospam.invalid> - 2016-12-22 19:30 -0500
Re: Android 6 Bill <Billaboard@gmail.com> - 2016-12-23 12:42 +0000
Re: Android 6 tlvp <mPiOsUcB.EtLlLvEp@att.net> - 2016-12-23 11:58 -0500
Re: Android 6 Arno Welzel <usenet@arnowelzel.de> - 2016-12-29 13:43 +0100
Re: Android 6 Daniel James <daniel@me.invalid> - 2016-12-30 15:34 +0000
Re: Android 6 Arno Welzel <usenet@arnowelzel.de> - 2016-12-30 22:33 +0100
Re: Android 6 Daniel James <daniel@me.invalid> - 2016-12-31 13:27 +0000
Re: Android 6 Arno Welzel <usenet@arnowelzel.de> - 2017-01-04 08:59 +0100
Re: Android 6 Daniel James <daniel@me.invalid> - 2017-01-04 13:40 +0000
Re: Android 6 Arno Welzel <usenet@arnowelzel.de> - 2017-01-11 09:00 +0100
Re: Android 6 Daniel James <daniel@me.invalid> - 2017-01-15 18:23 +0000
Re: Android 6 Arno Welzel <usenet@arnowelzel.de> - 2017-01-15 21:20 +0100
Re: Android 6 AL <45364747@invalid.com> - 2017-01-04 10:06 -0700
Re: Android 6 Arno Welzel <usenet@arnowelzel.de> - 2017-01-11 09:00 +0100
Re: Android 6 tlvp <mPiOsUcB.EtLlLvEp@att.net> - 2017-01-05 01:34 -0500
Re: Android 6 Daniel James <daniel@me.invalid> - 2017-01-07 14:14 +0000
Re: Android 6 tlvp <mPiOsUcB.EtLlLvEp@att.net> - 2017-01-07 13:09 -0500
Re: Android 6 Daniel James <daniel@me.invalid> - 2017-01-08 18:18 +0000
Re: Android 6 tlvp <mPiOsUcB.EtLlLvEp@att.net> - 2017-01-08 15:42 -0500
Re: Android 6 The Real Bev <bashley101@gmail.com> - 2017-01-08 17:11 -0800
Re: Android 6 nospam <nospam@nospam.invalid> - 2017-01-08 20:19 -0500
Re: Android 6 Daniel James <daniel@me.invalid> - 2017-01-09 23:55 +0000
Re: Android 6 Arno Welzel <usenet@arnowelzel.de> - 2017-01-11 18:07 +0100
Re: Android 6 Frank Slootweg <this@ddress.is.invalid> - 2017-01-08 21:34 +0000
Re: Android 6 Daniel James <daniel@me.invalid> - 2017-01-09 23:55 +0000
Re: Android 6 Joerg Lorenz <hugybear@gmx.ch> - 2016-12-24 10:49 +0100
Re: Android 6 Arno Welzel <usenet@arnowelzel.de> - 2016-12-22 23:55 +0100
Re: Android 6 nospam <nospam@nospam.invalid> - 2016-12-22 19:15 -0500
Re: Android 6 Joerg Lorenz <hugybear@gmx.ch> - 2016-12-23 05:46 +0100
Re: Android 6 nospam <nospam@nospam.invalid> - 2016-12-23 00:15 -0500
Re: Android 6 Dave Higton <dave@davehigton.me.uk> - 2016-12-23 17:11 +0000
Re: Android 6 nospam <nospam@nospam.invalid> - 2016-12-23 12:43 -0500
Re: Android 6 Dave Higton <dave@davehigton.me.uk> - 2016-12-23 21:22 +0000
Re: Android 6 nospam <nospam@nospam.invalid> - 2016-12-24 14:29 -0500
Re: Android 6 Dave Higton <dave@davehigton.me.uk> - 2016-12-25 11:10 +0000
Re: Android 6 Piet <www.godfatherof.nl/@opt-in.invalid> - 2016-12-25 12:37 +0100
Re: Android 6 nospam <nospam@nospam.invalid> - 2016-12-25 11:18 -0500
Re: Android 6 Dave Higton <dave@davehigton.me.uk> - 2016-12-25 20:28 +0000
Re: Android 6 nospam <nospam@nospam.invalid> - 2016-12-29 12:02 -0500
Re: Android 6 Arno Welzel <usenet@arnowelzel.de> - 2016-12-29 23:45 +0100
Re: Android 6 nospam <nospam@nospam.invalid> - 2016-12-29 18:02 -0500
Re: Android 6 Arno Welzel <usenet@arnowelzel.de> - 2016-12-30 22:24 +0100
Re: Android 6 nospam <nospam@nospam.invalid> - 2016-12-31 11:55 -0500
Re: Android 6 Arno Welzel <usenet@arnowelzel.de> - 2017-01-04 09:04 +0100
Re: Android 6 nospam <nospam@nospam.invalid> - 2017-01-04 10:14 -0500
Re: Android 6 Arno Welzel <usenet@arnowelzel.de> - 2017-01-11 18:11 +0100
Re: Android 6 nospam <nospam@nospam.invalid> - 2017-01-11 13:05 -0500
Re: Android 6 Arno Welzel <usenet@arnowelzel.de> - 2017-01-13 17:23 +0100
Re: Android 6 nospam <nospam@nospam.invalid> - 2017-01-16 15:35 -0500
Re: Android 6 Arno Welzel <usenet@arnowelzel.de> - 2017-01-17 05:39 +0100
Re: Android 6 Daniel James <daniel@me.invalid> - 2016-12-30 15:34 +0000
Re: Android 6 Arno Welzel <usenet@arnowelzel.de> - 2016-12-30 22:26 +0100
Re: Android 6 Daniel James <daniel@me.invalid> - 2016-12-31 13:27 +0000
Re: Android 6 nospam <nospam@nospam.invalid> - 2016-12-31 11:55 -0500
Re: Android 6 Arno Welzel <usenet@arnowelzel.de> - 2017-01-04 09:11 +0100
Re: Android 6 Daniel James <daniel@me.invalid> - 2017-01-04 13:40 +0000
Re: Android 6 nospam <nospam@nospam.invalid> - 2017-01-04 10:14 -0500
Re: Android 6 Arno Welzel <usenet@arnowelzel.de> - 2017-01-11 18:12 +0100
Re: Android 6 nospam <nospam@nospam.invalid> - 2017-01-11 13:05 -0500
Re: Android 6 Arno Welzel <usenet@arnowelzel.de> - 2017-01-13 17:24 +0100
Re: Android 6 Daniel James <daniel@me.invalid> - 2017-01-15 18:23 +0000
Re: Android 6 Arno Welzel <usenet@arnowelzel.de> - 2017-01-15 21:30 +0100
Re: Android 6 Daniel James <daniel@me.invalid> - 2017-01-16 15:42 +0000
Re: Android 6 nospam <nospam@nospam.invalid> - 2017-01-16 15:35 -0500
Re: Android 6 Arno Welzel <usenet@arnowelzel.de> - 2017-01-17 05:44 +0100
Re: Android 6 Daniel James <daniel@me.invalid> - 2017-01-17 17:47 +0000
Re: Android 6 Bill <Billaboard@gmail.com> - 2017-01-01 01:05 +0000
Re: Android 6 tlvp <mPiOsUcB.EtLlLvEp@att.net> - 2017-01-02 02:08 -0500
Re: Android 6 David Taylor <david-taylor@blueyonder.co.uk.invalid> - 2017-01-02 08:01 +0000
Re: Android 6 nospam <nospam@nospam.invalid> - 2017-01-02 08:51 -0500
Re: Android 6 Bill <Billaboard@gmail.com> - 2017-01-02 20:41 +0000
Re: Android 6 Arno Welzel <usenet@arnowelzel.de> - 2017-01-04 09:18 +0100
Re: Android 6 Arno Welzel <usenet@arnowelzel.de> - 2017-01-04 09:14 +0100
Re: Android 6 Arno Welzel <usenet@arnowelzel.de> - 2016-12-29 14:05 +0100
Re: Android 6 nospam <nospam@nospam.invalid> - 2016-12-29 12:02 -0500
Re: Android 6 Arno Welzel <usenet@arnowelzel.de> - 2016-12-29 23:46 +0100
Re: Android 6 Dave Higton <dave@davehigton.me.uk> - 2016-12-31 20:18 +0000
Re: Android 6 Arno Welzel <usenet@arnowelzel.de> - 2016-12-29 13:47 +0100
csiph-web