[prev in list] [next in list] [prev in thread] [next in thread] 

List:       taglib-devel
Subject:    Re: String::detach() not thread-safe?
From:       Scott Wheeler <wheeler () kde ! org>
Date:       2014-11-15 13:46:55
Message-ID: 443BD3DE-C30D-4412-8044-CDE3DD21D2C0 () kde ! org
[Download RAW message or body]


> On Nov 15, 2014, at 1:59 PM, Kevin André <hyperquantum@gmail.com> wrote:
> 
> With some googling I learned that multithreading issues in taglib were
> discussed before […]

Originally TagLib was never intended to be thread safe.  Little bits have \
been added over time, but they've mostly been band-aids.  At the time the \
main reason for that was that it didn't make sense to use TagLib from \
multiple threads:  for reading from a hard disk, it's a bad idea to read \
using multiple threads.  Tag reading isn't CPU bound except when all of the \
data is already in disk buffers and for disk IO, you'll get worse \
performance by doing heavy reading from multiple threads (it'll increase \
the number of seeks).  I don't know if this has changed with SSDs, but it'd \
be worth benchmarking before assuming "more concurrent threads" == "faster" \
in your application.  (Remember to purge the disk buffers before testing.)

-Scott

_______________________________________________
taglib-devel mailing list
taglib-devel@kde.org
https://mail.kde.org/mailman/listinfo/taglib-devel


[prev in list] [next in list] [prev in thread] [next in thread]