home.social

#binlog — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #binlog, aggregated by home.social.

  1. [Перевод] MariaDB 12.3: binlog внутри InnoDB

    Коротко для ленивых В MariaDB 12.3 binlog можно хранить внутри InnoDB через binlog_storage_engine=innodb . Главный эффект: вместо двух fsync() на commit остаётся один, поэтому на write-heavy нагрузке резко растут TPS и снижается tail latency. В тестах из статьи прирост на полном durability-профиле составил примерно 2.4x–3.3x . Backup, restore и ресинк реплик становятся проще, потому что binlog и данные теперь консистентны на уровне одного механизма хранения. Цена за это: обязателен GTID, Galera пока не поддерживается, а innodb_log_file_size нужно подбирать внимательнее из-за роста объёма redo. Если у вас обычная схема primary + async replica на InnoDB, эту возможность точно стоит хотя бы протестировать.

    habr.com/ru/articles/1011298/

    #MariaDB_123 #InnoDB #binlog #GTID #репликация #производительность_SQL #crash_recovery #fsync #OLTP

  2. [Перевод] MariaDB 12.3: binlog внутри InnoDB

    Коротко для ленивых В MariaDB 12.3 binlog можно хранить внутри InnoDB через binlog_storage_engine=innodb . Главный эффект: вместо двух fsync() на commit остаётся один, поэтому на write-heavy нагрузке резко растут TPS и снижается tail latency. В тестах из статьи прирост на полном durability-профиле составил примерно 2.4x–3.3x . Backup, restore и ресинк реплик становятся проще, потому что binlog и данные теперь консистентны на уровне одного механизма хранения. Цена за это: обязателен GTID, Galera пока не поддерживается, а innodb_log_file_size нужно подбирать внимательнее из-за роста объёма redo. Если у вас обычная схема primary + async replica на InnoDB, эту возможность точно стоит хотя бы протестировать.

    habr.com/ru/articles/1011298/

    #MariaDB_123 #InnoDB #binlog #GTID #репликация #производительность_SQL #crash_recovery #fsync #OLTP

  3. [Перевод] MariaDB 12.3: binlog внутри InnoDB

    Коротко для ленивых В MariaDB 12.3 binlog можно хранить внутри InnoDB через binlog_storage_engine=innodb . Главный эффект: вместо двух fsync() на commit остаётся один, поэтому на write-heavy нагрузке резко растут TPS и снижается tail latency. В тестах из статьи прирост на полном durability-профиле составил примерно 2.4x–3.3x . Backup, restore и ресинк реплик становятся проще, потому что binlog и данные теперь консистентны на уровне одного механизма хранения. Цена за это: обязателен GTID, Galera пока не поддерживается, а innodb_log_file_size нужно подбирать внимательнее из-за роста объёма redo. Если у вас обычная схема primary + async replica на InnoDB, эту возможность точно стоит хотя бы протестировать.

    habr.com/ru/articles/1011298/

    #MariaDB_123 #InnoDB #binlog #GTID #репликация #производительность_SQL #crash_recovery #fsync #OLTP

  4. [Перевод] MariaDB 12.3: binlog внутри InnoDB

    Коротко для ленивых В MariaDB 12.3 binlog можно хранить внутри InnoDB через binlog_storage_engine=innodb . Главный эффект: вместо двух fsync() на commit остаётся один, поэтому на write-heavy нагрузке резко растут TPS и снижается tail latency. В тестах из статьи прирост на полном durability-профиле составил примерно 2.4x–3.3x . Backup, restore и ресинк реплик становятся проще, потому что binlog и данные теперь консистентны на уровне одного механизма хранения. Цена за это: обязателен GTID, Galera пока не поддерживается, а innodb_log_file_size нужно подбирать внимательнее из-за роста объёма redo. Если у вас обычная схема primary + async replica на InnoDB, эту возможность точно стоит хотя бы протестировать.

    habr.com/ru/articles/1011298/

    #MariaDB_123 #InnoDB #binlog #GTID #репликация #производительность_SQL #crash_recovery #fsync #OLTP

  5. Pushed a big update to the MSBuild Log Viewer VS Code extension (still experimental!)

    - no more emoji - use VS Code icons
    - better display of search results in side view (and you can have multiple searches per binlog)
    - bookmarks! pin log items in the side view
    - long log entires open in real VS Code editor windows instead of in a div inside the binlog document

    marketplace.visualstudio.com/i

    #vscode #vscodeExtension #dotnet #msbuild #msbuildLogViewer #msbuildStructuredLogViewer #binlog

  6. So I made a thing...

    It's a VS Code extension based on Kirill Osenkov's @KirillOsenkov MS Build structured log viewer.

    marketplace.visualstudio.com/i

    The desktop version runs on CoreCLR, the insiders.vscode.dev version runs using the new (and still very experimental!) .NET 8 WASI workload on top of VS Code's WASI extension host (code.visualstudio.com/blogs/20)

    #vscode #dotnet #dotnet8 #net8 #wasi #coreclr #vscodeExtension #mono #msbuild #msbuildLogViewer #msbuildStructuredLogViewer #binlog

  7. So I made a thing...

    It's a VS Code extension based on Kirill Osenkov's @KirillOsenkov MS Build structured log viewer.

    marketplace.visualstudio.com/i

    The desktop version runs on CoreCLR, the insiders.vscode.dev version runs using the new (and still very experimental!) .NET 8 WASI workload on top of VS Code's WASI extension host (code.visualstudio.com/blogs/20)

    #vscode #dotnet #dotnet8 #net8 #wasi #coreclr #vscodeExtension #mono #msbuild #msbuildLogViewer #msbuildStructuredLogViewer #binlog

  8. So I made a thing...

    It's a VS Code extension based on Kirill Osenkov's @KirillOsenkov MS Build structured log viewer.

    marketplace.visualstudio.com/i

    The desktop version runs on CoreCLR, the insiders.vscode.dev version runs using the new (and still very experimental!) .NET 8 WASI workload on top of VS Code's WASI extension host (code.visualstudio.com/blogs/20)

    #vscode #dotnet #dotnet8 #net8 #wasi #coreclr #vscodeExtension #mono #msbuild #msbuildLogViewer #msbuildStructuredLogViewer #binlog

  9. So I made a thing...

    It's a VS Code extension based on Kirill Osenkov's @KirillOsenkov MS Build structured log viewer.

    marketplace.visualstudio.com/i

    The desktop version runs on CoreCLR, the insiders.vscode.dev version runs using the new (and still very experimental!) .NET 8 WASI workload on top of VS Code's WASI extension host (code.visualstudio.com/blogs/20)

    #vscode #dotnet #dotnet8 #net8 #wasi #coreclr #vscodeExtension #mono #msbuild #msbuildLogViewer #msbuildStructuredLogViewer #binlog

  10. If anyone wants samples of how to read MSBuild binlogs programmatically, the binlogtool project contains a bunch. Here's an example of dumping all properties and their values from a binlog:

    github.com/KirillOsenkov/MSBui

    binlogtool is a .NET tool, install using:

    `dotnet tool update -g binlogtool`

    #dotnet #msbuild #binlog

  11. One problem we have with #MSBuild #binlogs is when the MSBuild team updates the #binlog format, older versions of MSBuild.StructuredLogger NuGet package can't read the new format and blow up with an exception.

    People use the library in various CI and tools. I wish I had a way to notify them all to update the NuGet to latest, which adds support for the latest format. The library unfortunately can't be easily made forwards-compatible.

  12. Pushed a big update to the MSBuild Log Viewer VS Code extension (still experimental!)

    - no more emoji - use VS Code icons
    - better display of search results in side view (and you can have multiple searches per binlog)
    - bookmarks! pin log items in the side view
    - long log entires open in real VS Code editor windows instead of in a div inside the binlog document

    marketplace.visualstudio.com/i

    #vscode #vscodeExtension #dotnet #msbuild #msbuildLogViewer #msbuildStructuredLogViewer #binlog

  13. Pushed a big update to the MSBuild Log Viewer VS Code extension (still experimental!)

    - no more emoji - use VS Code icons
    - better display of search results in side view (and you can have multiple searches per binlog)
    - bookmarks! pin log items in the side view
    - long log entires open in real VS Code editor windows instead of in a div inside the binlog document

    marketplace.visualstudio.com/i

    #vscode #vscodeExtension #dotnet #msbuild #msbuildLogViewer #msbuildStructuredLogViewer #binlog

  14. Pushed a big update to the MSBuild Log Viewer VS Code extension (still experimental!)

    - no more emoji - use VS Code icons
    - better display of search results in side view (and you can have multiple searches per binlog)
    - bookmarks! pin log items in the side view
    - long log entires open in real VS Code editor windows instead of in a div inside the binlog document

    marketplace.visualstudio.com/i

    #vscode #vscodeExtension #dotnet #msbuild #msbuildLogViewer #msbuildStructuredLogViewer #binlog

  15. Pushed a big update to the MSBuild Log Viewer VS Code extension (still experimental!)

    - no more emoji - use VS Code icons
    - better display of search results in side view (and you can have multiple searches per binlog)
    - bookmarks! pin log items in the side view
    - long log entires open in real VS Code editor windows instead of in a div inside the binlog document

    marketplace.visualstudio.com/i

    #vscode #vscodeExtension #dotnet #msbuild #msbuildLogViewer #msbuildStructuredLogViewer #binlog

  16. If anyone wants samples of how to read MSBuild binlogs programmatically, the binlogtool project contains a bunch. Here's an example of dumping all properties and their values from a binlog:

    github.com/KirillOsenkov/MSBui

    binlogtool is a .NET tool, install using:

    `dotnet tool update -g binlogtool`

    #dotnet #msbuild #binlog

  17. If anyone wants samples of how to read MSBuild binlogs programmatically, the binlogtool project contains a bunch. Here's an example of dumping all properties and their values from a binlog:

    github.com/KirillOsenkov/MSBui

    binlogtool is a .NET tool, install using:

    `dotnet tool update -g binlogtool`

    #dotnet #msbuild #binlog

  18. If anyone wants samples of how to read MSBuild binlogs programmatically, the binlogtool project contains a bunch. Here's an example of dumping all properties and their values from a binlog:

    github.com/KirillOsenkov/MSBui

    binlogtool is a .NET tool, install using:

    `dotnet tool update -g binlogtool`

    #dotnet #msbuild #binlog

  19. If anyone wants samples of how to read MSBuild binlogs programmatically, the binlogtool project contains a bunch. Here's an example of dumping all properties and their values from a binlog:

    github.com/KirillOsenkov/MSBui

    binlogtool is a .NET tool, install using:

    `dotnet tool update -g binlogtool`

    #dotnet #msbuild #binlog

  20. One problem we have with #MSBuild #binlogs is when the MSBuild team updates the #binlog format, older versions of MSBuild.StructuredLogger NuGet package can't read the new format and blow up with an exception.

    People use the library in various CI and tools. I wish I had a way to notify them all to update the NuGet to latest, which adds support for the latest format. The library unfortunately can't be easily made forwards-compatible.

  21. One problem we have with #MSBuild #binlogs is when the MSBuild team updates the #binlog format, older versions of MSBuild.StructuredLogger NuGet package can't read the new format and blow up with an exception.

    People use the library in various CI and tools. I wish I had a way to notify them all to update the NuGet to latest, which adds support for the latest format. The library unfortunately can't be easily made forwards-compatible.

  22. One problem we have with #MSBuild #binlogs is when the MSBuild team updates the #binlog format, older versions of MSBuild.StructuredLogger NuGet package can't read the new format and blow up with an exception.

    People use the library in various CI and tools. I wish I had a way to notify them all to update the NuGet to latest, which adds support for the latest format. The library unfortunately can't be easily made forwards-compatible.

  23. One problem we have with #MSBuild #binlogs is when the MSBuild team updates the #binlog format, older versions of MSBuild.StructuredLogger NuGet package can't read the new format and blow up with an exception.

    People use the library in various CI and tools. I wish I had a way to notify them all to update the NuGet to latest, which adds support for the latest format. The library unfortunately can't be easily made forwards-compatible.