octave-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #53899] [octave forge] (io) Octave crashes whe


From: Philip Nienhuis
Subject: [Octave-bug-tracker] [bug #53899] [octave forge] (io) Octave crashes when writing large dbf files with dbfwrite
Date: Tue, 15 May 2018 14:51:20 -0400 (EDT)
User-agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:51.0) Gecko/20100101 Firefox/51.0 SeaMonkey/2.48

Update of bug #53899 (project octave):

                  Status:                    None => Need Info              

    _______________________________________________________

Follow-up Comment #2:

Just FTR, is this when writing to a spinning HD or to an SSD ?
I'm asking because we've seen reports before about problem relating to write
actions to SSD (in relation to zip & maybe gzip).

I never experienced this (yet) and I used to write huge shapefiles as well
with tens of attributes and >50,000 shape entries. My systems (Linux and
Windows) have SSDs but as of these days quite mediocre Core i5 CPUs. Maybe
your system is much faster and stumbles over the low level stuff and HW.

In several functions in the io package I had to introduce delays along the
line you sketch to overcome (what I interpret to be) lagging low-level/HW
responses so I'm not at all surprised. The big question is how long such a
delay should be in this case, as it is clearly system-dependent.

I do have plans to try collecting several writes into one bigger write action
to help speed up dbfwrite.m, by reducing overhead in the low-level routines (=
beyond Octave's control). Perhaps that would also solve this bug.

BTW hint: there's a much better shapewrite (and -read) in the mapping package
repo.


    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?53899>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/




reply via email to

[Prev in Thread] Current Thread [Next in Thread]