Tom,
Thanks! That's just what I wanted to hear! I'll look at upgrading this
weekend. I eventually gave up on trying to open a 130 MB file remotely
from my house this morning. I just had to kill the tab and reconnect.
To others, yes, I realize that the NFS is probably my biggest bottle
neck on the delete. Ultimately, I won't be using that. It was all I
had available at the time. We're planning to throw in another storage
array soon to handle more data.
I've been giving some thought to the long delete time issue and it seems
like the perfect example of when to use a message broker, especially if
you want this to scale well. The actual file system actions should be
in a different process altogether from the web front end. Instead it
should send a message to the back end process to delete the file and not
wait for the delete to actually complete.
It would be an interaction something like:
frontend: Am I authorized to delete file xxx?
backend: Yes.
frontend: Delete file xxx.
backend: Ok.
frontend removes file xxx from interface while backend is still deleting
the file. It doesn't have to wait for the deletion to complete.
It seems that this would be useful if you were trying to scale this up
over many, many servers.
You'll have to excuse me. I'm playing with RabbitMQ as a possible
method for "real time" data logging and analysis in our mobile lab. I
have no idea what I'm doing yet, but I'm probably full of useless
suggestions...among other things. (I was thinking hot air, but you can
visualize whatever substance you want.) :-)
Fred Bacon
Senior Scientist
Aerodyne Research, Inc.
On 2015-11-27 10:25 AM, Tom Needham wrote:
On 27 Nov 2015, at 14:38, bacon <[email protected]> wrote:
Which brings me to the second issue. If you accidentally try to open
a 130 MB text file via a web browser, the interface just comes to a
screeching halt. If you are extremely patient, the file will
eventually open after several minutes. Like about 10 minutes or so.
I don't know exactly because gave up timing it. The interface
doesn't give you any feedback about what is happening or a way to
cancel the action or even respond to any other interactions. It just
appears to freeze. When I inadvertently tried to open one of these
files in the web browser in front of one of the scientists, he got a
look of disgust and sneered that it seemed really slow. I tried to
explain that it was transferring 130 MB of data and formatting it
into html, but that is not a very satisfying excuse. Heck, I know
what's going on and it's still irksome to me.
Hey Fred,
In 8.2 I added a new version of the editor which includes loading
feedback and a limit to the file sizes to <4MB [1]. Apologies for
this!
Cheers,
Tom
[1]
https://github.com/owncloud/files_texteditor/blob/master/controller/filehandlingcontroller.php#L80
[1]
Links:
------
[1]
https://github.com/owncloud/files_texteditor/blob/master/controller/filehandlingcontroller.php#L80
_______________________________________________
User mailing list
[email protected]
http://mailman.owncloud.org/mailman/listinfo/user
