git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: On Tabs and Spaces

From
Linus Torvalds <torvalds@linux-foundation.org>
Date
Oct 17, 2007, 23:53 UTC
Message-ID
<alpine.LFD.0.999.0710171632200.26902@woody.linux-foundation.org>
In-Reply-To
<20071018011734.7b636141@localhost.localdomain>
On Thu, 18 Oct 2007, Christer Weinigel wrote:
> 
> BTW, how serious is the problem with deltifying when there are a lot of
> spaces that David Kastrup mentioned?
I suspect it works quite well in practice.

But we've had to tweak the xdiff code before, and the hash calculations for bucket size limits. If somebody actually points out a problem case, we can probably tweak it again.

> Wouldn't it be a problem when people put ASCII graphics in comments or 
> just have comments like /*********************************/ in their 
> code?

In general, *any* situation where you have tons of character sequences that are the same (and here it's not the characters *themselves* that have to be the same - it's the *sequence* that has to be the same, so it's not about repeating the same character over and over per se: it's about repeating a certain block of characters many many times in the source code) will be problematic for pretty much any similarity analysis.

Why? Because you just have a lot of the same sequence, and to get a good delta you want to find common "sequences of these sequences" (call them supersequences) in order to find the biggest common chunk.

So the badly performing cases for any delta algorithm (and I do want to point out that this has nothing what-so-ever to do with the particular one that git uses) tends to be exactly the ones where you have lots and lots of smaller chunks that match in two files, and that then makes it costlier to find the *bigger* chunks that are build up of those smaller chunks.

And generally you tend to have two situations: you either (a) take *much* longer to find the common areas (they are often quadratic or worse algorithms) or (b) you decide to ignore chunks that are so common that they don't really add any real information when it comes to finding truly common chunks. Where that second choice generally means that you can miss some cases where you *could* have found a good match for deltification.

In fact, usually you have a combination of the above two effects: certain deltas may be more expensive to find but there is also a limit that kicks in and means that you never spend *too* much time on finding them if the pattern space is not amenable to it.

Would lots of spaces be such a pattern? I personally doubt it would really matter. In general, source code is easy to delta: the bulk of any common sequences in most files will be found by the trivial "look for common sequences in the beginning and the end". The really *bad* cases tend to be rather odd, and often generated files.

So no, I don't think deltification is a huge deal for spaces. But it does boil down to the same kind of issues: if you blow up the source base by 20%, you often slow down things by 20% or more, simply because there is more data to process at all stages. It simply just slows down everything - totally unnecessarily.

			Linus
Previous: David KågedalNext: David Kastrup
Message 60 of 100 in “On Tabs and Spaces”
  1. Michael WittenOct 16, 2007
  2. Shawn O. PearceOct 16, 2007
  3. Michael WittenOct 16, 2007
  4. Andreas EricssonOct 16, 2007
  5. Sam RavnborgOct 16, 2007
  6. Petr BaudisOct 16, 2007
  7. DavidOct 17, 2007
  8. Andy ParkinsOct 17, 2007
  9. Adam PiatyszekOct 16, 2007
  10. Lars HjemliOct 16, 2007
  11. Adam PiatyszekOct 16, 2007
  12. Jeffrey C. OllieOct 16, 2007
  13. Michael WittenOct 16, 2007
  14. Jari AaltoOct 16, 2007
  15. Linus TorvaldsOct 16, 2007
  16. Mike HommeyOct 16, 2007
  17. Linus TorvaldsOct 16, 2007
  18. Linus TorvaldsOct 16, 2007
  19. Matthieu MoyOct 16, 2007
  20. Tom TobinOct 16, 2007
  21. Linus TorvaldsOct 16, 2007
  22. Christer WeinigelOct 16, 2007
  23. Linus TorvaldsOct 17, 2007
  24. Michael WittenOct 17, 2007
  25. Linus TorvaldsOct 17, 2007
  26. Luke LuOct 17, 2007
  27. Michael WittenOct 17, 2007
  28. Luke LuOct 17, 2007
  29. Nikolai WeibullOct 17, 2007
  30. Michael WittenOct 17, 2007
  31. Jari AaltoOct 17, 2007
  32. Andreas EricssonOct 17, 2007
  33. Jari AaltoOct 17, 2007
  34. Dmitry TorokhovOct 18, 2007
  35. Jari AaltoOct 18, 2007
  36. Petr BaudisOct 18, 2007
  37. Nikolai WeibullOct 18, 2007
  38. Miles BaderOct 22, 2007
  39. David KågedalOct 18, 2007
  40. Mike HommeyOct 18, 2007
  41. Jari AaltoOct 18, 2007
  42. Linus TorvaldsOct 17, 2007
  43. Johannes SchindelinOct 17, 2007
  44. Tom TobinOct 17, 2007
  45. Linus TorvaldsOct 17, 2007
  46. Tom TobinOct 17, 2007
  47. Linus TorvaldsOct 17, 2007
  48. Nicolas PitreOct 17, 2007
  49. Josh EnglandOct 17, 2007
  50. Linus TorvaldsOct 17, 2007
  51. Christer WeinigelOct 17, 2007
  52. Linus TorvaldsOct 17, 2007
  53. David KastrupOct 18, 2007
  54. Johannes SchindelinOct 17, 2007
  55. Christer WeinigelOct 17, 2007
  56. Johannes SchindelinOct 17, 2007
  57. Christer WeinigelOct 18, 2007
  58. Andreas EricssonOct 18, 2007
  59. David KågedalOct 18, 2007
  60. Linus TorvaldsOct 17, 2007
  61. David KastrupOct 17, 2007
  62. Johannes SchindelinOct 17, 2007
  63. Jan WielemakerOct 17, 2007
  64. Jeff KingOct 18, 2007
  65. Linus TorvaldsOct 18, 2007
  66. Jeff KingOct 18, 2007
  67. david@lang.hmOct 18, 2007
  68. Jeff KingOct 18, 2007
  69. Linus TorvaldsOct 18, 2007
  70. Linus TorvaldsOct 18, 2007
  71. Linus TorvaldsOct 18, 2007
  72. Jeff KingOct 18, 2007
  73. Add a message explaining that automatic GC is about to startkoreth@midwinter.com, Oct 18, 2007
  74. Steven GrimmOct 18, 2007
  75. Jeff KingOct 18, 2007
  76. Shawn O. PearceOct 18, 2007
  77. Brian GernhardtOct 18, 2007
  78. Steven GrimmOct 18, 2007
  79. Jeff KingOct 18, 2007
  80. Shawn O. PearceOct 19, 2007
  81. git-gc: improve wording of --auto notificationJeff King, Oct 19, 2007
  82. Shawn O. PearceOct 19, 2007
  83. Jeff KingOct 19, 2007
  84. Nicolas PitreOct 18, 2007
  85. Nicolas PitreOct 18, 2007
  86. Jeff KingOct 18, 2007
  87. Jeff KingOct 18, 2007
  88. David KastrupOct 17, 2007
  89. Nicolas PitreOct 17, 2007
  90. David KastrupOct 17, 2007
  91. SeanOct 17, 2007
  92. David KastrupOct 17, 2007
  93. Sam RavnborgOct 16, 2007
  94. Paul WankadiaOct 18, 2007
  95. Linus TorvaldsOct 18, 2007
  96. Dmitry PotapovOct 18, 2007
  97. Andreas EricssonOct 16, 2007
  98. Jan-Benedict GlawOct 16, 2007
  99. Andreas EricssonOct 16, 2007
  100. Robin RosenbergOct 20, 2007

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.