It is a real problem trying to edit a very large file with jedit. Files of 1 GB or more are almost impossible to edit, since the file needs at least 2 times the size of the file in maximum Java heap memory to edit. Even a file between 500 MB to 1 GB is difficult to edit as the end-user must increase the maximum Java heap memory to at least about 1200 MB to edit it. Files of 2 GB or more are impossible to edit because of the limitations of 32-bit heap memory allocation.
Jedit should be able to edit a file of any size, even if the size is greater than that of virtual memory. If a file is too large for the maximum amount of Java heap memory allocated Jedit should be able to edit the file by paging in whatever portion of the file is necessary to be viewed within any given Jedit buffer showing a portion of the file. The inability of jedit to edit any file size means that a programmer must use another editor to open files too large for Jedit to handle. This should be fixed in Jedit so that any size file can be edited by the editor. Even if paging in portions of a very large file slows down moving through the file a user of Jedit still should to edit a file of any allowable operating system size, and the end-user will accept slowdowns for very large files as long as editing the file does work correctly.
Log in to post a comment.