Skip to main content

High Throughput Computing week

We;ve just finished a week (well, four days) of talks, tutorials and discussion about High Throughput Computing. The event was opened by Miron Livny, leader of the Condor team, who gave an excellent introduction - the key point is that HTC is about the number of tasks that can be completed in a given time, whereas "traditional" High Performance Computing is about how much computing power can be brought to bear at a given time. As Miron puts it, Floating Operations per Year is not necessarily 60*60*24*7*52 Floating Operations per Second (FLOPS).

We've hosted events by the Condor team in the past, but for HTC week we extended our range. In particular, John Powers and Dan Ciruli of Digipede flew over from the Bay Area to tell us about their product. A day of hands-on tutorials allowed delegates to compare the strengths of Digipede and Condor, and the evening discussions included ways the systems could be used together.

Scheduled discussions looked at requirements for HTC in academia and in business, at Green IT, data handling and policy management. As one outcome of the discussions, we're looking to capture HTC design patterns, publish them on the web and incorporate them into training materials. On the academic side, we are planning to write a report to explain the policy issues to university heads of research computing.

There is talk of running this event again next year. We would like to extend the range of participants again, e.g. by looking to UnivaUD, DataSynapse or Platform. For more vendors to attend, we will need more commercial users, and vice versa, so we need to start encouraging people now. I'm wondering whether a small exhibition area might be useful to the commercial vendors and delegates - not a major trade show (with the concomitant expense) but enough to be an effective market place.

Watch this space - and get in touch if you're interested!


Popular posts from this blog

Changing Principles

In EA, architecture principles set a framework for making architectural decisions.  They help to establish a common understanding across different groups of stakeholders, and provide guidance for portfolios and projects.  Michael Durso of the LSE gave a good introduction to the idea in a webinar last week for the UCISA EA community.

Many organisations take the TOGAF architecture principles as a starting point.  These are based on the four architectural domains of TOGAF: business, information/data, applications, technology/infrastructure.  These principles tend to describe what should be done, e.g. re-use applications, buy in software rather than build it, keep data secure.  See for example the principles adopted at Plymouth University and the University of Birmingham.

Recently though, I encountered a different way of looking at principles.  The user experience design community tend to focus more on how we should do things.  E.g. we should start with user needs, use iterative developm…

A new EA Repository

One of my goals since starting this job two years ago has always been to create a repository for architecture documents.  The idea is to have a central store where people can find information about the University's applications, data sources, business processes, and other architectural information.  This store will make it easier for us to explain our plans, to show the current state of the University's information systems, and to explain what Enterprise Architecture is all about.

It's taken a long time to reach this goal, mainly because we're often had more pressing and immediate work to be done.  The creation of a repository is one of those tasks that is very important but never quite urgent.  So I'm now very happy to say that we are in the process of deploying a repository and modelling tool.

This is the culmination of a careful process to select the most appropriate tool for our needs.  We began by organising several workshops to gather requirements from a rang…

A brief summary of our major initiatives

I notice that in 2016 I wrote 34 posts on this blog.  This is only my fifth post in 2017 and we're already three-quarters of the way through the year.  Either I've suddenly got lazier, or else I've had less time to spend writing here.  As I'm not inclined to think of myself as especially lazy, I'm plumping for the latter explanation.

There really is a lot going on.  The University has several major initiatives under way, many of which need input from the Enterprise Architecture section.

The Service Excellence programme is overhauling (the buzzword is "transforming") our administrative processes for HR, Finance, and Student Administration.  Linked to this is a programme to procure an integrated ERP system to replace the adminstrative IT systems. 

Enabling Digital Transformation is a programme to put the middleware and architecture in place so that we can make our processes "digital first".  We're implementing an API framework, a notification…