Bugs item #3502940, was opened at 2012-03-12 15:00 Message generated for change (Comment added) made by franzzieris You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=843359&aid=3502940&group_id=167540
Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Performance Group: None Status: Open Resolution: None >Priority: 5 Private: No Submitted By: Stefan Rossbach (kargor) Assigned to: Nobody/Anonymous (nobody) Summary: "Scan Workspace" creates expensive file lists Initial Comment: This feature scans your current Eclipse workspace for a project that has the best match to the project that the inviter is send to you. Problem: the computeMatch computes a match based on the filenames. To compute the match, you need 2 file lists. When these file lists are created, the checksum calculation will be performed automatically. Scenario: My workspace constists of 10 projects, total size 2 GB and about 50000 files. If I press this button ... well, you can go and make you a cup of coffee. At least if you have a HDD and not a SSD. ---------------------------------------------------------------------- >Comment By: Franz Zieris (franzzieris) Date: 2012-05-23 08:59 Message: Since this only takes some time and doesn't actually harm anyone, I lowered the priority from 8 to 5. I just tested the master branch (Git 0b7b758) with a similar workspace (5 projects, 2 GB, 20000 files) and the scan took about 25 seconds. If somebody really uses a workspace that big he/she will understand that scanning this mammoth will take some time. ---------------------------------------------------------------------- Comment By: Stefan Rossbach (kargor) Date: 2012-03-13 15:57 Message: Please remove this feature and close this bug, ---------------------------------------------------------------------- Comment By: Alexander Waldmann (netcorps) Date: 2012-03-13 11:48 Message: This feature can be removed which i did in my prototype - no one missed it, no one used it more than once in the usability tests anyway. It is too slow to work for the average user. It isn't of help - manually choosing the locally existing project is much faster (user knows in most cases why he renamed it). Quickscan = compare projectname works in most cases. If there are two almost identical projects this yields undesired results: the first project is taken that matches by at least 80%, no further scanning is done, so if there is a project that appears in a later position in my workspace, it is not found. One of the useless functions that were introduced because (probably) ONE user asked for it, without thinking through if this actually helps (even that one user) or is yet another thing most users will never user / get confused by / ignore.. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=843359&aid=3502940&group_id=167540 ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Dpp-robot mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dpp-robot
