Is this slow speed really expected? Is there way to do the same thing faster?Īfter comment by Jeremey, if I comment all the work inside the loop (xmlFile.openXmlFile() and QStandardItem creation), it gets quite fast, takes like 3 seconds. Ui->labelXmlFileCount->setText( fileCount ) QString fileCount = QString("Total of %1 file(s) will be converted from `%2` folder").arg( QString::number(count), rootDir) 1.) Show folder size in a column From Q-Dir 3. The size of the program is slightly less than 500 Kb, but at the same time it significantly increases the convenience of working with files and folders. QDirIterator iter( rootDir, QStringList() lineEditSourceFolder->text() ) So the best solution is to only create filters that you truly need. Larger files can take a long time to archive. The inverse is also true of larger files.
The more filters you add the more validation checks need to be made. But when you have tens of thousands of files in a single folder, a simple folder list command (ls or dir) could take way too long. Adding too many filters slows down the package creation process. With less than 500 files, you might not notice any delays. EDIT: Oh, one thing popped on to my mind. However, every time when the OS will access the specific folder to search for files, it will have to process all files in the folder. If you truly want to keep the contents of those directories in RAM, you can put something like ls -lah /your/dir 2>&1 >/dev/null to your cron. XmlFileModel->clear() // xmlFileModel is QStanardItemModel Of course if everything is cached in RAM, this does not matter that much usually Linux caches frequently accessed files and dirs quite aggressively. Here is my function int MainWindow::searchXmlFiles(QString rootDir) I also changed the icons for folders and some file-types. I could put this in a thread but even than it will not be practical with this speed. Toward the end of the video, youll see a delay in files displaying in the right hand window. Get the answer to What is the best alternative to Q-Dir (the Quad. However, it is a known limitation that service definitions over 2 GB in size cannot be published when running Manager in the Internet Explorer or Firefox web browsers. I am iterating through all files in a folder (recursively though all its sub folders) but this is extremely almost never returns. Service definitions that contain source GIS datasets can take a long time to publish because the data must be transferred to the server.
0 kommentar(er)
