<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Optimistic shychronization in Intel® Moderncode for Parallel Architectures</title>
    <link>https://community.intel.com/t5/Intel-Moderncode-for-Parallel/Optimistic-shychronization/m-p/967588#M5459</link>
    <description>&lt;P&gt;Hello,&lt;BR /&gt;&lt;BR /&gt;I have come to an interresting subject...&lt;BR /&gt;&lt;BR /&gt;I was thinking more about my ParallelVarFiler and about database engines, first i have told you that since database engines are disk &lt;BR /&gt;bound and/or memory bound that means that they are not scalable &lt;BR /&gt;in multicores systems, but more than that that i was thinking more&lt;BR /&gt;and asking my self why to use optimistic synchronization mechanism like in transactional memory ? i think that an optimistic synchronization mechanism like in transactional memory can give better throughput and better speed, prof of that ? take a look at my ParallelVarFiler for exemple, &lt;BR /&gt;since it can be disk bound when you are saving automaticly the &lt;BR /&gt;data to a disk file that means that there is no need to use &lt;BR /&gt;an RWLock since the hardisk is not trully parallel.. so a Lock will have &lt;BR /&gt;the same performance as an RWLock in a disk bound scenario, it's why i have used a FIFO fair Lock inside my ParallelVarFiler, but if the hardisk or memory can be truly parallel an RWLock will be better , &lt;BR /&gt;it's the same with an optimistic sychronization like in transactional memory, first you have to know that a Lock will serialize the read and write transactions, an RWLock will parallelize the read transaction, but&amp;nbsp; with optimistic synchronization mechanism like in transactional memory you can have in theory many writes transactions in parallel &lt;BR /&gt;and many read transactions in parallel , but since the hardisk is not truly parallel, this &lt;BR /&gt;optimistic synchronization like in transactional memory will not bring &lt;BR /&gt;better performance than a RWLock , so i think that transactional memory and &lt;BR /&gt;optimistic synchronization can not give better performance if the hardisk and memory are not trully parallel, but since the memory system &lt;BR /&gt;and hardisk system is not truly parallel today, so this &lt;BR /&gt;optmistic schychronisation that is using transactional memory or other systemes, will not bring you better performance than a RWLock.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Thank you,&lt;BR /&gt;Amine Moulay Ramdane.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;</description>
    <pubDate>Mon, 28 Oct 2013 03:00:44 GMT</pubDate>
    <dc:creator>aminer10</dc:creator>
    <dc:date>2013-10-28T03:00:44Z</dc:date>
    <item>
      <title>Optimistic shychronization</title>
      <link>https://community.intel.com/t5/Intel-Moderncode-for-Parallel/Optimistic-shychronization/m-p/967588#M5459</link>
      <description>&lt;P&gt;Hello,&lt;BR /&gt;&lt;BR /&gt;I have come to an interresting subject...&lt;BR /&gt;&lt;BR /&gt;I was thinking more about my ParallelVarFiler and about database engines, first i have told you that since database engines are disk &lt;BR /&gt;bound and/or memory bound that means that they are not scalable &lt;BR /&gt;in multicores systems, but more than that that i was thinking more&lt;BR /&gt;and asking my self why to use optimistic synchronization mechanism like in transactional memory ? i think that an optimistic synchronization mechanism like in transactional memory can give better throughput and better speed, prof of that ? take a look at my ParallelVarFiler for exemple, &lt;BR /&gt;since it can be disk bound when you are saving automaticly the &lt;BR /&gt;data to a disk file that means that there is no need to use &lt;BR /&gt;an RWLock since the hardisk is not trully parallel.. so a Lock will have &lt;BR /&gt;the same performance as an RWLock in a disk bound scenario, it's why i have used a FIFO fair Lock inside my ParallelVarFiler, but if the hardisk or memory can be truly parallel an RWLock will be better , &lt;BR /&gt;it's the same with an optimistic sychronization like in transactional memory, first you have to know that a Lock will serialize the read and write transactions, an RWLock will parallelize the read transaction, but&amp;nbsp; with optimistic synchronization mechanism like in transactional memory you can have in theory many writes transactions in parallel &lt;BR /&gt;and many read transactions in parallel , but since the hardisk is not truly parallel, this &lt;BR /&gt;optimistic synchronization like in transactional memory will not bring &lt;BR /&gt;better performance than a RWLock , so i think that transactional memory and &lt;BR /&gt;optimistic synchronization can not give better performance if the hardisk and memory are not trully parallel, but since the memory system &lt;BR /&gt;and hardisk system is not truly parallel today, so this &lt;BR /&gt;optmistic schychronisation that is using transactional memory or other systemes, will not bring you better performance than a RWLock.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Thank you,&lt;BR /&gt;Amine Moulay Ramdane.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 28 Oct 2013 03:00:44 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Moderncode-for-Parallel/Optimistic-shychronization/m-p/967588#M5459</guid>
      <dc:creator>aminer10</dc:creator>
      <dc:date>2013-10-28T03:00:44Z</dc:date>
    </item>
  </channel>
</rss>

