<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>data management systems on DASYA</title>
    <link>https://dasya.itu.dk/tags/data-management-systems/</link>
    <description>Recent content in data management systems on DASYA</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <copyright>© DASYA, IT University of Copenhagen</copyright>
    <lastBuildDate>Wed, 05 Aug 2026 00:00:00 +0000</lastBuildDate>
    
	<atom:link href="https://dasya.itu.dk/tags/data-management-systems/index.xml" rel="self" type="application/rss+xml" />
    
    
    <item>
      <title>Flexible Data Placement on SSDs for Database Systems</title>
      <link>https://dasya.itu.dk/for-students/proposals/current/pito-fdpsim-duckdb/</link>
      <pubDate>Wed, 05 Aug 2026 00:00:00 +0000</pubDate>
      
      <guid>https://dasya.itu.dk/for-students/proposals/current/pito-fdpsim-duckdb/</guid>
      <description>Traditionally solid-state drives (SSDs) does not give the users the ability to control the data placement on the SSD. This often leads to suboptimal performance and lowers SSD lifetime, since SSDs internally don&amp;rsquo;t allow in-place updates. The updated disk pages are written elsewhere and the old versions have to be garbage collected. This poses problems if data with different lifetimes and update frequencies often gets written in the same region.</description>
    </item>
    
    <item>
      <title>Alternative IO backends for Database Systems and SSDs</title>
      <link>https://dasya.itu.dk/for-students/proposals/archive/pito-xnvme-duckdb/</link>
      <pubDate>Tue, 15 Jul 2025 00:00:00 +0000</pubDate>
      
      <guid>https://dasya.itu.dk/for-students/proposals/archive/pito-xnvme-duckdb/</guid>
      <description>A recent MSc thesis project at ITU integrated xNVMe to DuckDB. DuckDB, like many popular database systems, rely on a syncronous IO backend and the POSIX filesystem interfaces for its ease of use. xNVMe, in contrast, allows a unified interface for alternative and more performant IO backends such as io-uring and spdk. Thus, integration of xNVMe into DuckDB offers interesting avenues for data analytics workloads run on DuckDB.
The existing integration of xNVMe to DuckDB is preliminary.</description>
    </item>
    
    <item>
      <title>Flexible Data Placement on SSDs for Database Systems</title>
      <link>https://dasya.itu.dk/for-students/proposals/archive/pito-fdp-duckdb/</link>
      <pubDate>Mon, 13 May 2024 00:00:00 +0000</pubDate>
      
      <guid>https://dasya.itu.dk/for-students/proposals/archive/pito-fdp-duckdb/</guid>
      <description>Traditionally solid-state drives (SSDs) does not give the users the ability to control the data placement on the SSD. This often leads to suboptimal performance and lowers SSD lifetime, since SSDs internally don&amp;rsquo;t allow in-place updates. The updated disk pages are written elsewhere and the old versions have to be garbage collected. This poses problems if data with different lifetimes and update frequencies often gets written in the same region.</description>
    </item>
    
  </channel>
</rss>