Bioinformatics.org
[Regeneron]
[Repositive.io]
[OMICtools]
Not logged in
  • Log in
  • Bioinformatics.org
    Membership (39402+) Group hosting [?] Wiki
    Franklin Award
    Sponsorships

    Careers
    About bioinformatics
    Bioinformatics training
    Bioinformatics jobs

    Research
    All information groups
    Online databases Online analysis tools Online education tools More tools

    Development
    All software groups
    FTP repository
    SVN & CVS repositories [?]
    Mailing lists

    Forums
    News & Commentary
  • Submit
  • Archives
  • Subscribe

  • Jobs Forum
    (Career Center)
  • Submit
  • Archives
  • Subscribe
  • BIRCH: Comprehensive bioinfo. system - Support tickets

    Submit | Open tickets | Closed tickets

    [ Ticket #1149 ] Virtual machine lag in testing
    Date:
    08/19/11 00:25
    Submitted by:
    umhameld
    Assigned to:
    umhameld
    Category:
    Winbirch
    Priority:
    1
    Ticket group:
    Getbirch
    Resolution:
    Not Resolved
    Summary:
    Virtual machine lag in testing
    Original submission:
    This is not explicitly a bug, it is more a development issue that becomes apparent in testing.

    Winbirch runs *extremely* slowly in a virtual machine. The main issue, i believe, is I/O overhead due to lack of hardware support (not introduced until the i7 generation of chips).

    Evidence of this is the fact that it takes 150-200 minutes to install birch in a virtual machine, due to the untar-ing overhead. On a physical machine, installs are usually clocked at less than 10 minutes.

    This makes development slow and sluggish as forces a batch-job approach for development.

    I recommend we find an old windows box, core2 due generation, for very cheap (~300 dollars), and set it up on a local subnet, using one of our terminals (probably albacore) as a gateway into it (for security reasons - having 2 doors instead of 1). This would reduce I/O overhead, and make local access very quick.

    I am however marking this as low priority, as it is a suggestion and not a necessity. As other developers come to winbirch (brian, graham), I just want to bring this up as a potential issue to with the workflow. It exclusively applies to getbirch, and I think it will become a factor in testing binaries on windows, and the installer in general.
    Please log in to add comments and receive followups via email.
    No followups have been posted

    1 - 1 of 1

    Dependent on ticket
    Winbirch priority
       
    No results for "Dependent on Task"
    No other tickets are dependent on this ticket
    Ticket change history
    Field Old value Date By
    priority 2 03/16/15 17:57 B_Fristensky
    status_id Pending 08/19/11 00:26 umhameld
    priority 5 08/19/11 00:26 umhameld
    assigned_to unset 08/19/11 00:26 umhameld
    resolution_id Unset 08/19/11 00:26 umhameld

     

    [G6GFindr]
    Copyright © 2017 · Scilico, LLC