[mk01]

(3rd Dec, 2013 08:09 PM)Smultie Wrote:  I guess I was one on the persons complaining about really slow apt-get in beta 1.1
Haven't experienced it (yet) in Beta2 but before it looked like it got slower over time.

Yes, sorry Smultie - specially not reminding you

in general this 'fact' will stay - as we still use btrfs - which is b-tree COW filesystem - and using APT-GET and having SNAPSHOTS. one would call it killer combo.

as:
1) COW will re-write ALL data or METADATA for single smallest file change
2) APT_GET by design unpacks a copy for all existing package files, then creates links and then don't know. already there it is terrible
3) each snapshot means metadata record of single data stored somewhere, during update in any snapshot, all related records across snapshots gets updated with new info (not data, but metadata is enough) and if filesystem is mounted with atime or even relatime (accessing file means it's metadata change which will cause update / recheck across snapshots which will cause .... it's like never ending techno party)

We did our best to help as much as possible, at least we tried. FS is remounted with noatime after boot. FS doesn't contain DOUBLE metadata structure for SSD/SD drives. Metadata blocks are larger (4x) to generate less IO and LIMIT the problematic metadata fragmentation.

I had no more ideas in this area. Definitely not easy fight with old simple filesystems like extX. But they are scary.

---

(3rd Dec, 2013 09:30 PM)badmonkey Wrote:  I'm just updating library on boot with the standard option, no extra addons - everything seems to work fine though, it's just different to pre beta 2 where the time was right on boot.

you can consider the date added meaning switch. it has one big advantage though - if you lose your lib an d decide to rescrap, the old way will change the order in recently added. totally. if you change date added to mean file creation time, this will stay constant. do the best for you.

as for different behavior. there is not much to do, ntod will not sync quicker than 40-50s,. but beta2 is attaching network faster, xbmc is starting sooner and faster.

for time being you can add "started ntp" ti other start on stanzas in /etc/init/xbmc.conf. during next days we can implement this as user configurable option (ti wait fir REAL time ti be acquired). this can take hours in case time diff is big (RFC documents).

other option could be use ntpdate instead of ntpd 0 ntpdate is not following the rules and is doing big time jumps without hesitate.

let's thing about all this few days,.