maindavfs2 - Support: sr #108778, Cache clean and CPU spike blocks...

 
 

sr #108778: Cache clean and CPU spike blocks transfers

Submitter:  None
Submitted:  Wed 25 Mar 2015 10:39:43 PM UTC
   
 
Category:  None Priority:  5 - Normal
Severity:  3 - Normal Status:  In Progress
Privacy:  Public Assigned to:  _71007
Originator Email:  -email is unavailable- Open/Closed:  Closed
Operating System:  GNU/Linux
* Mandatory Fields

Add a New Comment Rich Markup
   

Fri 27 Mar 2015 04:41:47 PM UTC, comment #2: 

Yes delay_upload 0.
With delay_upload 0 is the write considered complete when it writes to the davfs2 cache or when it writes to the remote Webdav server?

"Independent from the cache and any options: the transfer rate to the server will limit the overall write speed of your davfs2 file system."
Transfer rate to what serer?  To the davfs2 server or from the davfs2 server to the webdav server?

We check the uploads based on folder/volume size and they are matching.  We don't have any files in lost+found.

We found with delay_upload 1, the files were taking a long time to get uploaded to the webdav server from the davfs2 server.

I thank you in advance.
Any idea when you will be making it multi threaded?  I guess it's a lot of work.  cash incentive?  :)


Thanks


Aneil <asingh>
Fri 27 Mar 2015 08:00:09 AM UTC, comment #1: 

davfs2 is still single threaded. While an upload is in progress the file system interface will block.

"Uploads=0"? Did you mean option "delay_upload 0"?
With this option davfs2 will upload the file when it is closed. The file system interface will block until the upload finished.

Independent from the cache and any options: the transfer rate to the server will limit the overall write speed of your davfs2 file system.

Did you check that uploads work at all? Sometimes uploads don't work because of server bugs like not supporting conditional uploads. You should check directory lost+found. If there are files in this directory then there is a problem with the server. You should also use some other client to check wether files are transferred to the server at all.

Werner

- <_71007>
Wed 25 Mar 2015 10:39:43 PM UTC, original submission:  

We have tried many different setting with table_size and cache_size.

We are copying files and every once in a while the cache cleans which drives the CPU but then it blocks the client from transmitting still.

Uploads=0 as we want to upload immediately.
Locks are off.

How can I get this to continue to accept files into the buffer and transfer while the cache is being cleaned up?


THanks

Anonymous

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:
   
   
Comment:
   

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by asingh (Posted a comment)
  • -email is unavailable- added by _71007 (Posted a comment)
  • -email is unavailable- added by None (Submitted the item)
  •  

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

    Only logged-in users can vote.

     

    Follow 4 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2019-12-26 _71007 Open/ClosedOpen Closed
    2015-03-27 _71007 Severity5 - Blocker 3 - Normal
        StatusNone In Progress
        Assigned toNone _71007

    Back to the top

    Powered by Savane 3.13-f8d8.
    Corresponding source code